-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
XContent: Trying to use a writer with date formats results in serialization issues #31853
Comments
Pinging @elastic/es-core-infra |
the issue for this is, that the date transformers (where there is one for Instant) only are checked if you use This used to work under 6.2 and fails under 6.3 |
Note that this change affects ML watches created via the Kibana UI, see elastic/kibana#18376 |
Similar thing happens in Java API, if I build a query with |
this also affects users with watches that were created and properly running in 5.x and now fail under 6.3 |
This ensures that the java time class exposed by painless have proper serialization/string representations. Closes elastic#31853
Would this also cause watches created by an ML job in 6.3 to not execute properly as well? Error is: |
Just answered my own question by reading more carefully in the thread. |
This ensures that the java time class exposed by painless have proper serialization/string representations. Closes #31853
This ensures that the java time class exposed by painless have proper serialization/string representations. Closes #31853
This ensures that the java time class exposed by painless have proper serialization/string representations. Closes #31853
fails under 6.3.1/6.3.0.
results in
exact stack trace
The text was updated successfully, but these errors were encountered: