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.

Sign up for GitHub

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

Jump to bottom

SQL: Fix deserialization issue of TimeProcessor #40776

Merged
merged 2 commits into from
Apr 3, 2019
Merged

SQL: Fix deserialization issue of TimeProcessor #40776

merged 2 commits into from
Apr 3, 2019

Commits on Apr 3, 2019

  1. SQL: Fix deserialization issue of TimeProcessor 

    TimeProcessor didn't implement `getWriteableName()` so the one from
the parent was used which returned the `NAME` of the parent. This
caused `TimeProcessor` objects to be deserialised into
DateTimeProcessor.

Moreover, added a restriction to run the TIME related integration tests
only in UTC timezone.

Fixes: elastic#40717
    @matriv
    matriv committed Apr 3, 2019
    Configuration menu
    Copy the full SHA
    e8ab7ca View commit details
    Browse the repository at this point in the history

  2. Address comment

    @matriv
    matriv committed Apr 3, 2019
    Configuration menu
    Copy the full SHA
    6c53bd4 View commit details
    Browse the repository at this point in the history