[
https://issues.apache.org/jira/browse/CALCITE-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158790#comment-16158790
]
Aman Sinha commented on CALCITE-1975:
-------------------------------------
Drill's ANY type is treated as a primitive type (with nullability) and yes in
the past we have had to make changes (or request changes) in Calcite's CASTing
rules. However, we also have an implementation of
{{org.apache.calcite.sql.type.SqlReturnTypeInference}} to override the type
inferencing rules. From Calcite's perspective, a more generalized framework
could be along the lines of user-defined types but that would be lot of work.
Extending ANY type to be composite type instead of primitive could be a
reasonable alternative.
> make some method in SqlTypeFactoryImpl public
> ---------------------------------------------
>
> Key: CALCITE-1975
> URL: https://issues.apache.org/jira/browse/CALCITE-1975
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Ruidong Li
> Assignee: Julian Hyde
>
> Some other project which use calcite may have it's own logic in
> {{leastRestrictiveByCast}} and {{leastRestrictiveSqlType}}. For example,
> Flink's {{ANY}} SqlType differs from calcite's , it'e better to implementing
> it's own logic.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
