-
Notifications
You must be signed in to change notification settings - Fork 5
3.5 - Integrating latest from neo4j/3.5 #75
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
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* document branching policy * Styling & Language & one sentence per line Co-authored-by: Michael Hunger <github@jexp.de>
The procedure now yeilds batchComputationResult in line with what is documented. Co-authored-by: Håkan Löfqvist <hakan.lofqvist@neo4j.com>
Co-authored-by: Håkan Löfqvist <hakan.lofqvist@neo4j.com>
* ensure tombstone is sent, adding `queueCapacity` parameter * prevent QueueBasedSpliterator from waiting forever * Using a state variable QueueBasedSpliterator knows if it already has seen tombstone. * using poll/offer instead of put/take for queues
The kernel event handling creates a big expensive transaction snapshot for every transaction if there are registered event handlers. To avoid paying that overhead, unregister from the kernel if there are no triggers. This works as a complement to the config option, so you can deploy large groups of databases with the config enabled but only pay the overhead on those databases that use trigger. This is backporting the respective commit from 4.0 branch.
export test would otherwise complain about permissions
ThomasMatlak
reviewed
May 1, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.