Lockdown _timestamp field
#11794
Merged
Lockdown _timestamp field
#11794
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
rjernst
added
v2.0.0-beta1
:Search Foundations/Mapping
|
LGTM |
rjernst
force-pushed
the
fix/lockdown-timestamp
branch
from
fde058b to
291a308
Compare
This is a follow up to elastic#8143 and elastic#6730 for _timestamp. It removes support for `path`, as well as any field type settings, and enables docvalues for _timestamp, for 2.0. Users who need to adjust these settings can use a date field.
rjernst
force-pushed
the
fix/lockdown-timestamp
branch
from
291a308 to
12e7cbe
Compare
clintongormley
changed the title
_timestamp field
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.
This is a follow up to #8143 and #6730 for _timestamp. It removes
support for
path, as well as any field type settings, andenables docvalues for _timestamp, for 2.0. Users who need to
adjust these settings can use a date field.