JodaCompatibleZonedDateTime in Elasticsearch 6.5.x breaks scripts with "The datetime zone id 'Z' is not recognised" #36306
Labels
:Core/Infra/Scripting
Scripting abstractions, Painless, and Mustache
Elasticsearch version 6.5.1
Plugins installed: []
JVM version JVM 1.8.0_191
OS version Windows 10
Description of the problem including expected versus actual behavior:
We use scripting with date functions in some code. When we try to upgrade to Elasticsearch 6.5.1, one of our unit tests fails with the following exception:
Steps to reproduce:
The following also reproduces this for me, it seems Joda does not know about the special "Z" timezone identifier, but Java Time uses it:
It seems this was introduced with the Java-time-compatibility layer in commit 758a6f5 and 3046656, PR #33486
A more elaborate integration test that works at least in Elasticsearch 6.2.4, but fails with Elasticsearch 6.5.1:
The text was updated successfully, but these errors were encountered: