[
https://issues.apache.org/jira/browse/FLINK-39123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18060426#comment-18060426
]
Rion Williams edited comment on FLINK-39123 at 2/23/26 5:58 PM:
----------------------------------------------------------------
[~twalthr]
I've gone ahead and [crafted a PR|https://github.com/apache/flink/pull/27650]
that I believe should address this. It looked like the previous behavior was
explicitly capping the precision level for the timestamps at 3, whereas this
proposed update would remove that restriction and generate a corresponding
`TIMESTAMP_WITH_LOCAL_TIME_ZONE` instance.
I'm not sure if there are any additional places where we would need to make
these changes or related documentation, if necessary. I've added you as a
reviewer and would appreciate any feedback or guidance if you get a chance.
was (Author: rionmonster):
[~twalthr]
I've gone ahead and crafted a PR that I believe should address this. It looked
like the previous behavior was explicitly capping the precision level for the
timestamps at 3, whereas this proposed update would remove that restriction and
generate a corresponding `TIMESTAMP_WITH_LOCAL_TIME_ZONE` instance.
I'm not sure if there are any additional places where we would need to make
these changes or related documentation, if necessary. I've added you as a
reviewer and would appreciate any feedback or guidance if you get a chance.
> ValueLiteralExpression.asSerializableString has problems with TIMESTAMP_LTZ(9)
> ------------------------------------------------------------------------------
>
> Key: FLINK-39123
> URL: https://issues.apache.org/jira/browse/FLINK-39123
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API
> Reporter: Timo Walther
> Assignee: Timo Walther
> Priority: Major
> Labels: pull-request-available
>
> Seems the method needs an update from latest Calcite updates.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
