[
https://issues.apache.org/jira/browse/CALCITE-5570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17699870#comment-17699870
]
Julian Hyde commented on CALCITE-5570:
--------------------------------------
[~zabetak], We're using slightly different terminology - what I call a type
constructor (in the [Standard ML sense|http://mlton.org/TypeConstructor]) is
what you would call a type definition minus the angle brackets and arguments,
{{UNIONTYPE}} for example - but we are in agreement that those things should
use angle brackets.
[~Sergey Nuyanzin], Yes {{MULTISET<INTEGER>}} should be a synonym for INTEGER
MULTISET. My list wasn't exhaustive.
> Support nested map type for SqlDataTypeSpec
> -------------------------------------------
>
> Key: CALCITE-5570
> URL: https://issues.apache.org/jira/browse/CALCITE-5570
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Sergey Nuyanzin
> Assignee: Jiajun Xie
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> There was added a similar support for arrays/multisets at
> https://issues.apache.org/jira/browse/CALCITE-3250
> however there is no support for maps so far.
> The issue is to add such support.
>
> I think I'd like to clarify is syntax for maps since it has 2 internal
> subtypes for keys and values may be something similar to ROW with delimiter
> like
> {code:sql}
> SELECT CAST(NULL AS MAP(INT, INT));
> -- or with square brackets similar to map constructor
> SELECT CAST(NULL AS MAP[INT, INT]);
> -- or with angle (Flink syntax)
> SELECT CAST(NULL AS MAP<INT, INT>);
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
