-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[Java.time] Support partial parsing #46814
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
Conversation
Pinging @elastic/es-core-infra |
c351638
to
6055a82
Compare
Any idea when 7.5.0 will be released (weeks/months)? This is somewhat of a blocker for us migrating off 5.x |
@elasticmachine update branch |
@elasticmachine run elasticsearch-ci/packaging-sample-matrix |
@niemyjski it is really hard to tell, could be either weeks/month. You can always try to workaround with your own custom date format. |
I don't want to have to do this on every date field that I have, and then have to reindex every index when this fix is out. |
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
Enable partial parsing of date part. This is making the behaviour in java.time implementation the same as with joda. 2018, 2018-01 and 2018-01-01 are all valid dates for date_optional_time or strict_date_optional_time closes elastic#45284 closes elastic#47473
Enable partial parsing of date part. This is making the behaviour in java.time implementation the same as with joda.
2018, 2018-01 and 2018-01-01 are all valid dates for
date_optional_time
orstrict_date_optional_time
closes #45284
closes #47473