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.
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
TSDB: add index timestamp range check #78291
TSDB: add index timestamp range check #78291
Changes from 23 commits
2bad389
8809757
6c42357
c3f1e66
79e96e0
b4a68c3
63e552c
0e67726
e3b7256
78c132d
fe8f654
120cdaf
563ca87
daccfb7
14a2378
2c45c57
d2a00ec
d631649
1dcebb0
79db882
69df14d
6c77b18
40f2e82
582588f
bfe25c5
6350ee1
a5a116f
7236ee1
20c21a8
9e92d09
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I'm worried that right now these can't be
null
so all indices are going to validate the range. I wonder if we can convert these tonull
for the defaults so we disable the validation when it isn't set.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.
I know I wrote this, but on further reading, I think maybe it makes sense to just move it all to
DataStreamTimestampFieldMapper
. I thought I was being clever, but all of this code should be able to run just fine from there and it'd be nice thatDateFieldMapper
doesn't need to care about the validation.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.
I agree with moving this logic to
DataStreamTimestampFieldMapper
, since there there is already validation for the@timestamp
field (whether it exists and whether a single value has been specified). And I think at least initially, tsdb will work only with data streams.