[ 
https://issues.apache.org/jira/browse/CALCITE-5570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700800#comment-17700800
 ] 

Julian Hyde edited comment on CALCITE-5570 at 3/15/23 5:52 PM:
---------------------------------------------------------------

I wonder whether it's possible to make MapSqlType, ArraySqlType, 
MultisetSqlType extend ApplySqlType? Also, should SqlTypeName have a field that 
is the number of type parameters (0 for most, 1 for measure, array and 
multiset, 2 for map)?

Note that array should continue to unparse as 'T ARRAY', but we should parse 
both 'T ARRAY' and 'ARRAY<T>'. Similarly MULTISET.


was (Author: julianhyde):
I wonder whether it's possible to make MapSqlType, ArraySqlType, 
MultisetSqlType extend ApplySqlType? Also, should SqlTypeName have a field that 
is the number of type parameters (0 for most, 1 for measure, array and 
multiset, 2 for map)?

> 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: 50m
>  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)

Reply via email to