8000 Fix erroneous "access after data-modification" errors by jsteemann · Pull Request #14646 · arangodb/arangodb · GitHub
[go: up one dir, main page]

Skip to content

Fix erroneous "access after data-modification" errors #14646

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

Prev Previous commit
Next Next commit
Merge branch 'devel' of github.com:arangodb/arangodb into bug-fix/rem…
…ove-unnecessary-checks-for-access-after-modification
  • Loading branch information
jsteemann committed Aug 16, 2021
commit bd17edf353ccfead7761a396a1a027ac1dd6e53d
5 changes: 4 additions & 1 deletion CHANGELOG
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
devel
-----

<<<<<<< HEAD
* Some AQL queries erroneously reported the "access after data-modification"
error for queries in which there was a read attempt from a collection
_before_ a data-modification operation. Such access is legal and should not
Expand All @@ -10,6 +10,9 @@ devel
* Bugfix: In more complex queries there was a code-path where a (Disjoint-)
Smart graph access was not properly optimized.

* Fixed: _api/transaction/begin called on edge collections of disjoint
SmartGraphs falsely returned CollectionNotFound errors.

* Improve log messages for Pregel runs by giving them more context.

* Add ReplicatedLogs column family.
Expand Down
You are viewing a condensed version of this merge commit. You can view the full changes here.
0