[
https://issues.apache.org/jira/browse/CALCITE-976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15009387#comment-15009387
]
Julian Hyde commented on CALCITE-976:
-------------------------------------
We need a test. In SqlValidatorTest, how about validating a UNION ALL with an
ANY column on one side.
Why do you make an ANY type always nullable?
> Sql ANY type handling when find least restrictive type or add cast function
> ---------------------------------------------------------------------------
>
> Key: CALCITE-976
> URL: https://issues.apache.org/jira/browse/CALCITE-976
> Project: Calcite
> Issue Type: Bug
> Reporter: Jinfeng Ni
> Assignee: Julian Hyde
>
> This comes from a commit in Drill's forked Calcite
> (https://github.com/dremio/calcite/commit/32accb4ca09b8b1029caf6d1c3cc5a6010106b86)
> 1) When one input type is ANY, SqlTypeFactoryImpl.leastRestrictiveSqlType()
> should return ANY.
> 2) Do not create CAST() function, if target type is ANY.
> [~mehant], could you please submit a PR after rebasing ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
