Utilizing the Neo4j transactional HTTP endpoint #22
Conversation
This file contains 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
|
So we were actually previously using the transactional API, but we found the batch API to be significantly faster and easier to use. We'll have to play around with this for a bit first. |
|
Thanks for the pull. After talking with @rvazarkar/@andyrobbins and testing, we'll go ahead and land this as the batch API is being depreciated. |
porterhau5
pushed a commit
to porterhau5/BloodHound
that referenced
this pull request
Oct 22, 2017
Utilizing the Neo4j transactional HTTP endpoint
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.
Ran into some issues with the 'db/data/batch' API call and stumbled across the transactional HTTP endpoint (http://neo4j.com/docs/developer-manual/3.0/http-api/#http-api-transactional).
Code works, but probably needs some reviewing.