feat: ensure 6 miliseconds supported #486
Draft
Conversation
This file contains hidden or 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
YuriZmytrakov
force-pushed
the
CAT-1449-2
branch
from
ef66c7d to
ad81f26
Compare
Updated datetime to `strict_date_optional_time_nanos` for microsecond precision and replaced infinite/overflow values with 2262-04-11T23:47:16.854775Z to prevent format errors after reindexing.
YuriZmytrakov
force-pushed
the
CAT-1449-2
branch
from
c8c09de to
da110dc
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description:
Ensure the filter supports 6 digit precision by updating
datetimeformat tostrict_date_optional_time_nanosfor microsecond precision and replacing infinite or overflow values with the max supported Elasticsearch date2262-04-11T23:47:16.854775Z, otherwise after reindex users will encounter a datetime format error:PR Checklist:
pre-commit run --all-files)make test)