Update this for indradb 4 #3
Open
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
…needs error handling.
…uestions remain open.
Fix/update to new indra api
This reverts commit b734999.
Fixup all unit tests in the suite.
…Edge properties and vertex properties missing due to complex insertion mechanic.
Improved performance of property/property-value iteration on vertices
Fix/update to new indra api
…separate repo easier.
|
|
Speedup the bulk import process
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.
This PR updates the sled-backend for indradb version 4.0.0.
The current choice of "indexing" is to always prefix-index for any property and just keep the indexes in a table for now to fulfill the behavior desired by the indradb-tests.
We can totally discuss this choice :)