You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (Jira)" <ji...@apache.org> on 2023/06/10 20:38:00 UTC
[jira] [Resolved] (CALCITE-5755) Add to Sarg serialization/deserialization TimestampString
[ https://issues.apache.org/jira/browse/CALCITE-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Hyde resolved CALCITE-5755.
----------------------------------
Fix Version/s: 1.35.0
Resolution: Fixed
Fixed in [0f682017|https://github.com/apache/calcite/commit/0f682017238b7965555f854605d9f4d5d4c0963f].
> Add to Sarg serialization/deserialization TimestampString
> ---------------------------------------------------------
>
> Key: CALCITE-5755
> URL: https://issues.apache.org/jira/browse/CALCITE-5755
> Project: Calcite
> Issue Type: Sub-task
> Reporter: Oliver Lee
> Assignee: Oliver Lee
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.35.0
>
>
> Currently Sarg serialization/deserialization allows for 6 types [https://github.com/apache/calcite/blob/967bb5acc5448bc8d6ee9b9f5fa3c5f0d71405c2/core/src/main/java/org/apache/calcite/rel/externalize/RelJson.java#L113] and doesn't include {{TimestampString}}
>
> Currently when a timestamp string comes in, it will not throw an error, but will deserialize incorrectly as a {{Date}} set to the epoch beginning.
> Desired outcome: Be able to serialize / deserialize SEARCH operators that contain Timestamp string literals.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)