Ran Tao created CALCITE-6061:
--------------------------------
Summary: MapValueConstrcutor/MapQueryConstructor use LinkedHashMap
erroneously
Key: CALCITE-6061
URL: https://issues.apache.org/jira/browse/CALCITE-6061
Project: Calcite
Issue Type: Bug
Affects Versions: 1.35.0
Reporter: Ran Tao
when we call:
{code:java}
select map[1,2,3,4];{code}
The order of results returned is the same every time. because calcite use
LinkedHashMap for storage. But semantically, the order should not be guaranteed
just like MULTISET.
we can see other engines such as apache spark/flink just use HashMap in this
case.
[https://github.com/apache/flink/blob/a2681f6a85aaad21179f91e03a91b4a05158841e/flink-table/flink-table-planner/src/main/scala/org/apache/flink/table/planner/codegen/ExprCodeGenerator.scala#L711]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)