8000 Feature/parallel aql phase one 2 by jsteemann · Pull Request #10408 · arangodb/arangodb · GitHub
[go: up one dir, main page]

Skip to content

Feature/parallel aql phase one 2 #10408

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 14 commits into from
Nov 12, 2019
Merged

Conversation

jsteemann
Copy link
Contributor

No description provided.

@jsteemann jsteemann added this to the devel milestone Nov 12, 2019
@jsteemann jsteemann merged commit d400830 into devel Nov 12, 2019
@jsteemann jsteemann deleted the feature/parallel-aql-phase-one-2 branch November 12, 2019 14:47
ObiWahn added a commit that referenced this pull request Nov 14, 2019
…nto feature/switch-some-scripts-to-python3

* 'devel' of https://github.com/arangodb/arangodb: (107 commits)
  fix description of NetworkFeature options
  Bug fix/dont use indexes in progress (#10432)
  rename `lib_libarango_shell` to `libarango_shell`. (#10433)
  fix issues found by cppcheck (#10434)
  Remove IndexHandle (#10424)
  fix invalid assertion (#10429)
  no coordinators left behind (#10422)
  fix compile warning in AnalyzerFeature test
  allow using `RANDOM_TOKEN` AQL function with an argument value of `0`. (#10414)
  centralize cloning functionality for AstNodes (#10430)
  Don't modify a finalized node. (#10419)
  Bug fix/internal issue #651 (#10415)
  show index type in not implemented exception (#10426)
  Parallel SortingGatherExecutor (#10410)
  "run with --log v8=debug" to see the stacktraces of logged error messages (#10373)
  ARANGODB_UPGRADE_DURING_RESTORE env variable. (#10385)
  add optional exclusive writes to rocksdb engine (#10364)
  attempt to make test more deterministic
  Feature/parallel aql phase one 2 (#10408)
  Improve syncer error message (#10403)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0