[
https://issues.apache.org/jira/browse/FLINK-39244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Walther closed FLINK-39244.
--------------------------------
Fix Version/s: 2.3.0
Release Note: TO_TIMESTAMP_LTZ() function now supports up to precision 9
for both numeric and string conversions. While we kept backwards compatibility
for numeric precision 0-3 which always returns TIMESTAMP_LTZ(3), precisions
p=4-9 now return TIMESTAMP_LTZ(p). Function calls taking string formats such as
".SSSS" now return precision 4 instead of silently loosing sub second
information.
Resolution: Fixed
Fixed in master: 25493ac2a95b52421631293705c24fceb40b51f4
> Support precision 0-9 for TO_TIMESTAMP_LTZ function
> ---------------------------------------------------
>
> Key: FLINK-39244
> URL: https://issues.apache.org/jira/browse/FLINK-39244
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: Ramin Gharib
> Assignee: Ramin Gharib
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.3.0
>
>
> Currently, TO_TIMESTAMP_LTZ(numeric, precision) only supports precision
> values of 0 (seconds) and 3 (milliseconds). This limits users who need to
> work with higher-precision epoch values such as microseconds or nanoseconds.
> This change extends TO_TIMESTAMP_LTZ to support all precision values from 0
> to 9, where the precision parameter specifies the unit of the epoch value as
> 10^(-precision) seconds:
> - 0 = seconds
> - 3 = milliseconds
> - 6 = microseconds
> - 9 = nanoseconds
> - Other values (1, 2, 4, 5, 7, 8) are also supported
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
