[
https://issues.apache.org/jira/browse/FLINK-17151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327916#comment-17327916
]
Flink Jira Bot commented on FLINK-17151:
----------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Align Calcite's and Flink's SYMBOL types
> ----------------------------------------
>
> Key: FLINK-17151
> URL: https://issues.apache.org/jira/browse/FLINK-17151
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / API
> Reporter: Dawid Wysakowicz
> Priority: Major
> Labels: stale-major
>
> Flink's `SymbolType` stores the class of the symbol. Calcite does not. When
> converting from Flink's to Calcite's type we are loosing that information. We
> should either remove that from the Flink's type or add it to Calcite's.
> I am in favor of removing it from the {{SymbolType}}. This type is a pseudo
> type which can be used only for literals. The symbol class is already part of
> the corresponding value, therefore it is a redundant information in the type
> itself.
> Initial discussion:
> https://github.com/apache/flink/pull/11694#discussion_r408058640
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
