[ 
https://issues.apache.org/jira/browse/CALCITE-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jess Balint updated CALCITE-3489:
---------------------------------
    Description: 
-when adding day to timestamp, the day interval is not converted to ms, in the 
generated code I see "-2208944806000L + 2L;" where 2 is the number of days. 
same for hour/minute/second. the return value is the original timestamp (at 
least when represented as a string, perhaps the two ms are added to it)-

the query I was using is more like {{timestamp '2014-02-11 00:00:00' + cast('1' 
as interval day)}} (I have a custom convertlet creating this expression). the 
CAST here is creating an interval value, but we expect it to be processed as in 
SqlToRexNodeConverterImpl (which turns it into milliseconds)

  was:when adding day to timestamp, the day interval is not converted to ms, in 
the generated code I see "-2208944806000L + 2L;" where 2 is the number of days. 
same for hour/minute/second. the return value is the original timestamp (at 
least when represented as a string, perhaps the two ms are added to it)


> Cast to interval is ignored
> ---------------------------
>
>                 Key: CALCITE-3489
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3489
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.21.0
>            Reporter: Jess Balint
>            Priority: Major
>              Labels: correctness, datetime
>
> -when adding day to timestamp, the day interval is not converted to ms, in 
> the generated code I see "-2208944806000L + 2L;" where 2 is the number of 
> days. same for hour/minute/second. the return value is the original timestamp 
> (at least when represented as a string, perhaps the two ms are added to it)-
> the query I was using is more like {{timestamp '2014-02-11 00:00:00' + 
> cast('1' as interval day)}} (I have a custom convertlet creating this 
> expression). the CAST here is creating an interval value, but we expect it to 
> be processed as in SqlToRexNodeConverterImpl (which turns it into 
> milliseconds)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to