Fix index values #338
Merged
Fix index values #338
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
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.
Due to the addition of the
optimizeTopKkey in the index creation result (since 3.12 EE), some of our tests are failing. This PR acknowledges the existence of that key explicitly.Also, I propagated the warning on the usage of hash and skiplist indexes to our driver. Currently users are not affected, but a first step is to remove their usages from our documentation and indicate a proper alternative. At some point, we'll have to patch these methods to use the
persistentindex internally, and eventually remove them from the driver.