[
https://issues.apache.org/jira/browse/CALCITE-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169919#comment-15169919
]
Julian Hyde commented on CALCITE-1102:
--------------------------------------
Disabled ANY functionality as part of the fix for CALCITE-1054. Improved code
generation for handling NULL values broke the previous shaky implementation of
ANY.
> Add implementations of built-in operators applied to ANY type
> -------------------------------------------------------------
>
> Key: CALCITE-1102
> URL: https://issues.apache.org/jira/browse/CALCITE-1102
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
>
> The support for the ANY type in built-in operators is not reliable. Such
> operators validate successfully but in the Enumerable convention are likely
> to generate code that is invalid. This is especially true for overloaded
> operators, where the implementation of the operator needs to be determined
> based on the runtime type of the operands.
> We have disabled SqlOperatorTest.testPlusOperatorAny. When fixing this issue
> look for other disabled tests tagged with this JIRA case number.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
