refactor!: CreateIndexOp returns string, CreateIndexesOp returns array #2666
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
mbroadst
suggested changes
Dec 8, 2020
mbroadst
suggested changes
Dec 10, 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.
CreateIndexesOperationwas returning the name of the created indexinstead of the result from the server because of the logic ensuring
CreateIndexOperationhas that behavior.This PR makes
CreateIndexesOperationreturn an array of index names(breaking change), while
CreateIndexOperationcontinues to return asingle index name string. This makes the behavior consistent with other
official drivers.
Users in need of the raw result from the server should use
db.command.NODE-2602