[6.x] test: hard code esApiVersion to master #13198
Merged
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
Until elasticsearch.js actually has support for 6.x/6.0 branches, this needs to just rely on the master apiVersion. Also, we shouldn't change this esApiVersion in tests unless we are also changing the value in our elasticsearch plugin proper, otherwise our tests can accidentally use a different API version than reality.
|
cc @spalger |
epixa
added a commit
that referenced
this pull request
Jul 28, 2017
Until elasticsearch.js actually has support for 6.x/6.0 branches, this needs to just rely on the master apiVersion. Also, we shouldn't change this esApiVersion in tests unless we are also changing the value in our elasticsearch plugin proper, otherwise our tests can accidentally use a different API version than reality.
|
6.0 7ee7cd7 |
epixa
changed the title
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.
Until elasticsearch.js actually has support for 6.x/6.0 branches, this
needs to just rely on the master apiVersion.
Also, we shouldn't change this esApiVersion in tests unless we are also
changing the value in our elasticsearch plugin proper, otherwise our
tests can accidentally use a different API version than reality.