-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use mappings to format doc-value fields by default. #30831
Merged
Merged
Changes from 12 commits
Commits
Show all changes
43 commits
Select commit
Hold shift + click to select a range
9d01696
Use mappings to format doc-value fields by default.
jpountz 7140149
iter
jpountz 4b85e3f
Merge branch 'master' into remove_use_field_mapping
jpountz b062fd6
iter
jpountz 3fe4b44
Merge branch 'master' into remove_use_field_mapping
jpountz 92696e9
iter
jpountz 7f71843
Merge branch 'master' into remove_use_field_mapping
jpountz ec5633f
iter
jpountz 32c7259
Merge branch 'master' into remove_use_field_mapping
jpountz 519517b
iter
jpountz 20fd918
iter
jpountz 5fdd429
iter
jpountz 635e0a1
iter
jpountz 4868ce1
Merge branch 'master' into remove_use_field_mapping
jpountz 202ff72
Merge branch 'master' into remove_use_field_mapping
jpountz 2832a35
Merge branch 'master' into remove_use_field_mapping
jpountz 335fd33
Merge branch 'master' into remove_use_field_mapping
jpountz 20e7f13
iter
jpountz 6e57e47
iter
jpountz cbbca3e
iter
jpountz e39ee37
Merge branch 'master' into remove_use_field_mapping
jpountz 63fabee
Merge branch 'master' into remove_use_field_mapping
jpountz 2956352
iter
jpountz 3d17141
Merge branch 'master' into remove_use_field_mapping
jpountz 9b96e10
iter
jpountz 4650a46
Merge branch 'master' into remove_use_field_mapping
jpountz 091d195
iter
jpountz 30922bf
iter
jpountz 39e7f86
Merge branch 'master' into remove_use_field_mapping
jpountz 854951f
iter
jpountz 31f87b4
Merge branch 'master' into remove_use_field_mapping
jpountz 48aacd6
iter
jpountz 6ab4b74
Merge branch 'master' into remove_use_field_mapping
jpountz 8f2329f
iter
jpountz d6200ad
Merge branch 'master' into remove_use_field_mapping
jpountz da84b02
iter
jpountz 0223f75
Merge branch 'master' into remove_use_field_mapping
jpountz 8fd2457
Merge branch 'master' into remove_use_field_mapping
jpountz 6da6920
iter
jpountz 2ae65cc
iter
jpountz 00fc077
Merge branch 'master' into remove_use_field_mapping
jpountz c49e621
iter
jpountz 60cb3e4
fix test failure
jpountz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure but should we have a test to check for warnings that runs on 6.4-7.0 versions for the mixed cluster bwc tests?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A test that would have "6.3.99 - 6.99.99" as a version would never run since 7.0 is not included?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmmm I think I might have a slightly misunderstanding on how the mixed cluster tests work then as I thought we set up a mixed cluster (let say 5 modes with 3 as 6.x and 2 as 7.0) and then we ran the YAML tests against the 6.x nodes using the 6.x version to work out which tests to run. Though now that I'm writing this I realise that as long as the 6.x version tests that the warning is sent (which it does) it should be enough and we probably shouldn't have 7.0 effectively test somethign in 6.x.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Weeps I had missed that you were talking specifically about the bw tests. Yes, my preference would be to not test the warning, especially as things might depend on which node acts as a coordinating node for the search request.