Hi, I'm investigating the behavior of the functions timestampdiff with
different time-units.
I found that in the case of the time-units: second, minute, hour, and day, the
logical plan returned by Calcite is consistent. Since the input is a timestamp
in milliseconds, in the same way, the
r hand, instead of creating a new intermidiate pogical
> > project,
> > > we can also update ProjectTableScanRule to accept LogicalProject that is
> > > not a simple mapping, and do the same task I mentioned above.
> > >
> > > - Haisheng
> > >
>
>
> > > > On the other hand, instead of creating a new intermidiate pogical
> > > project,
> > > > we can also update ProjectTableScanRule to accept LogicalProject that
> > is
> > > > not a simple mapping, and do the same task I mentioned above.
> > > >
>
Hi, maybe you can help me.
I have this portion from a larger logical plan:
..
LogicalProject(l_orderkey=[$0], l_suppkey=[$2], *=[*($5, -(1, $6))])
LogicalTableScan(table=[[main, lineitem]])
..
Because the LogicalProject above contains an evaluation, the
