Tomasz Gawęda created CALCITE-7829:
--------------------------------------
Summary: RexSimplify rewrites Date to int
Key: CALCITE-7829
URL: https://issues.apache.org/jira/browse/CALCITE-7829
Project: Calcite
Issue Type: Bug
Reporter: Tomasz Gawęda
In Hazelcast we have a test called RowAssignmentTypeCoercionTest. When trying
to upgrade to Calcite 1.42 we've noticed, that some cases fail (despite working
previously).
For example, queries:
CREATE MAPPING m type IMap OPTIONS('keyFormat'='int', 'valueFormat'='java',
'valueJavaClass'='com.hazelcast.jet.sql.impl.support.expressions.ExpressionValue$ObjectVal')
SINK INTO m VALUES(0, cast('01:42:00' as time), 0)
translate to:
```
LogicalTableSink(table=[[hazelcast, public, m[projects=[$0, $1, $2, $3]]]],
operation=[INSERT], flattened=[false])
LogicalCalc(expr#0=[\{inputs}], expr#1=[0], expr#2=[6120000],
expr#3=[CAST($t2):OBJECT], expr#4=[null:OBJECT], __key=[$t1], field1=[$t3],
key=[$t1], this=[$t4])
LogicalValues(tuples=[[\{ 0 }]])
```
As you can see, `01:42:00` was translated to 6120000. This integer value is
then written to a field of type OBJECT.
Previously, in 1.39 dates and times landed in "object" field with their real
types, not converted to integer, which makes me believe, that RexSimplify
tries. to simplify a bit too much.
(cast(cast('01:42:00' as time) as object) = time written to object column, not
integer value.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
