[
https://issues.apache.org/jira/browse/CALCITE-7567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Nuyanzin updated CALCITE-7567:
-------------------------------------
Description:
The issue is that if there is {{TIMESTAMP}} and {{TIMESTAMP_LTZ}} with
different precision
for instance {{TIMESTAMP(3)}} and {{TIMESTAMP_LTZ(0)}}
{{leastRestrictive}} from {{TIMESTAMP(3)}} and {{TIMESTAMP_LTZ(0)}}
and {{leastRestrictive}} from {{TIMESTAMP_LTZ(0)}} and {{TIMESTAMP(3)}}
return different results.
In the latest one there will be {{leastRestrictive}} with precision 0
was:
The issue is that if there is {{TIMESTAMP}} and {{TIMESTAMP_LTZ}} with
different precision
for instance {{TIMESTAMP(3)}} and {{TIMESTAMP_LTZ(0)}}
{{leastRestrictive}} from TIMESTAMP(3) and TIMESTAMP_LTZ(0)
and {{leastRestrictive}} from TIMESTAMP_LTZ(0) and TIMESTAMP(3)
return different results.
In the latest one there will be leastRestrictive with precision 0
> LeastRetrictiveSqlType for TIMESTAMP, TIMESTAMP_LTZ might ignore precision
> --------------------------------------------------------------------------
>
> Key: CALCITE-7567
> URL: https://issues.apache.org/jira/browse/CALCITE-7567
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Sergey Nuyanzin
> Assignee: Sergey Nuyanzin
> Priority: Major
>
> The issue is that if there is {{TIMESTAMP}} and {{TIMESTAMP_LTZ}} with
> different precision
> for instance {{TIMESTAMP(3)}} and {{TIMESTAMP_LTZ(0)}}
> {{leastRestrictive}} from {{TIMESTAMP(3)}} and {{TIMESTAMP_LTZ(0)}}
> and {{leastRestrictive}} from {{TIMESTAMP_LTZ(0)}} and {{TIMESTAMP(3)}}
> return different results.
> In the latest one there will be {{leastRestrictive}} with precision 0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
