-
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
Ensure parameters are updated when merging flattened mappings. #48971
Merged
jtibshirani
merged 1 commit into
elastic:master
from
jtibshirani:merge-flattened-fields
Nov 12, 2019
Merged
Ensure parameters are updated when merging flattened mappings. #48971
jtibshirani
merged 1 commit into
elastic:master
from
jtibshirani:merge-flattened-fields
Nov 12, 2019
+51
−9
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
jtibshirani
added
>bug
:Search Foundations/Mapping
Index mappings, including merging and defining field types
v8.0.0
v7.6.0
labels
Nov 11, 2019
Pinging @elastic/es-search (:Search/Mapping) |
This PR makes the following two fixes around updating flattened fields: * Make sure that the new value for ignore_above is immediately taken into affect. Previously we recorded the new value but did not use it when parsing documents. * Allow depth_limit to be updated dynamically. It seems plausible that a user might want to tweak this setting as they encounter more data.
jtibshirani
force-pushed
the
merge-flattened-fields
branch
from
November 12, 2019 17:50
8dd68fe
to
bd85f89
Compare
@elasticmachine run elasticsearch-ci/1 |
jimczi
approved these changes
Nov 12, 2019
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.
LGTM
@elasticmachine run elasticsearch-ci/packaging-sample-matrix |
Thanks @jimczi for the review. |
jtibshirani
added a commit
that referenced
this pull request
Nov 13, 2019
… (#49014) This PR makes the following two fixes around updating flattened fields: * Make sure that the new value for ignore_above is immediately taken into affect. Previously we recorded the new value but did not use it when parsing documents. * Allow depth_limit to be updated dynamically. It seems plausible that a user might want to tweak this setting as they encounter more data.
This was referenced Feb 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>bug
:Search Foundations/Mapping
Index mappings, including merging and defining field types
v7.6.0
v8.0.0-alpha1
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 makes the following two fixes around updating flattened fields:
ignore_above
is immediately taken intoaffect. Previously we recorded the new value but did not use it when parsing
documents.
depth_limit
to be updated dynamically. It seems plausible that a usermight want to tweak this setting as they encounter more data.
Addresses #48907.