-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
Change the maximum digits in a year to 4 #54260
Conversation
We changed the default joda behaviour in strict_date_optional_time to max 4 digits in a year. This helps parsing epoch_millis format which is often used in a default format `strict_date_optional_time||epoch_millis` This change adjustes our java.time implmementation to behave the same way
Pinging @elastic/es-core-infra (:Core/Infra/Core) |
Changing to 4 digit year seems ok to me, but I don't recall exactly why we allowed 10 digits in the first place. I vaguely remember this being joda behavior we were matching. @spinscale do you remember at all why we do the above? I'm also unsure to what extent we can make this change in 7.x, since it is technically breaking? I think we would need a proper deprecation period and possibly a flag so users can opt in to the newer behavior. |
ok to test |
closing in favour of #73034 |
We changed the default joda behaviour in strict_date_optional_time to
max 4 digits in a year. This helps parsing epoch_millis format which is
often used in a default format
strict_date_optional_time||epoch_millis
This change adjustes our java.time implmementation to behave the same
way
closes #52396