is intentional or not but I
> >> guess you can have a look at the changes landed around
> >> RexSimplify/RexExecutor.
> >>
> >> Best,
> >> Stamatis
> >>
> >> [1]
> >>
> >>
> https://github.com/apache/calcite/blob/812e3e98
>> Stamatis
>>
>> [1]
>>
>> https://github.com/apache/calcite/blob/812e3e98eae518cf85cd1b6b7f055fb96784a423/core/src/main/java/org/apache/calcite/rex/RexLiteral.java#L357
>>
>>
>> On Thu, Feb 10, 2022 at 8:02 AM Chathura Widanage <
>> chathuraw
ttps://github.com/apache/calcite/blob/812e3e98eae518cf85cd1b6b7f055fb96784a423/core/src/main/java/org/apache/calcite/rex/RexLiteral.java#L357
>
>
> On Thu, Feb 10, 2022 at 8:02 AM Chathura Widanage <
> chathurawidan...@gmail.com> wrote:
>
> > Hi community,
> >
&
gt;
> > I'm comparing two rel expressions generated by calcite 1.25.0 and 1.29.0
> > and noticed there is an invalid IntervalSQLType plugged into the query.
> >
> > <=($6, 1998-09-02 00:00:00) : Calcite 1.25.0
> > vs
> > <=($6, CAST(-(1998-12-01, 777600:INTERVAL DAY)):TIME
calcite 1.25.0 and 1.29.0
> and noticed there is an invalid IntervalSQLType plugged into the query.
>
> <=($6, 1998-09-02 00:00:00) : Calcite 1.25.0
> vs
> <=($6, CAST(-(1998-12-01, 777600:INTERVAL DAY)):TIMESTAMP(0) NOT NULL)
> :
> Calcite 1.29.0
>
> 777600 is
Hi community,
I'm comparing two rel expressions generated by calcite 1.25.0 and 1.29.0
and noticed there is an invalid IntervalSQLType plugged into the query.
<=($6, 1998-09-02 00:00:00) : Calcite 1.25.0
vs
<=($6, CAST(-(1998-12-01, 777600:INTERVAL DAY)):TIMESTAMP(0) NOT NULL) :
C
