Skip to content
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

Fix Joda compatibility in stream protocol #53823

Merged
merged 1 commit into from
Mar 19, 2020

Conversation

rjernst
Copy link
Member

@rjernst rjernst commented Mar 19, 2020

The JodaCompatibleZonedDateTime is a compatibility object that unions
Joda's DateTime and Java's ZonedDateTime, meant for use in scripts. When
it was added, we serialized the JCZDT as a Joda DateTime so that when
sending to older nodes they could still read the object. However, on
newer nodes, we continued also reading this as a Joda DateTime. This
commit changes the read side to form a JCZDT.

closes #53586

The JodaCompatibleZonedDateTime is a compatibility object that unions
Joda's DateTime and Java's ZonedDateTime, meant for use in scripts. When
it was added, we serialized the JCZDT as a Joda DateTime so that when
sending to older nodes they could still read the object. However, on
newer nodes, we continued also reading this as a Joda DateTime. This
commit changes the read side to form a JCZDT.

closes elastic#53586
@rjernst rjernst added >bug :Core/Infra/Core Core issues without another label v8.0.0 v7.7.0 labels Mar 19, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (:Core/Infra/Core)

Copy link
Contributor

@jdconrad jdconrad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks for fixing this.

@rjernst rjernst merged commit c2ae78d into elastic:master Mar 19, 2020
@rjernst rjernst deleted the joda_compat_stream branch March 19, 2020 22:05
rjernst added a commit that referenced this pull request Mar 19, 2020
The JodaCompatibleZonedDateTime is a compatibility object that unions
Joda's DateTime and Java's ZonedDateTime, meant for use in scripts. When
it was added, we serialized the JCZDT as a Joda DateTime so that when
sending to older nodes they could still read the object. However, on
newer nodes, we continued also reading this as a Joda DateTime. This
commit changes the read side to form a JCZDT.

closes #53586
@pgomulka
Copy link
Contributor

pgomulka commented Mar 20, 2020

@rjernst does this mean that the problem from #53823 was only exposed in a mixed cluster?
ok I tested this in a same version cluster and the fix will apply there too
thanks for fixing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Scripting error "dynamic method [org.joda.time.DateTime, toInstant/0] not found"
5 participants