[
https://issues.apache.org/jira/browse/CALCITE-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15621525#comment-15621525
]
Julian Hyde edited comment on CALCITE-1453 at 10/31/16 7:45 AM:
----------------------------------------------------------------
Fixed in http://git-wip-us.apache.org/repos/asf/calcite/commit/80240720, with a
small fix-up in
http://git-wip-us.apache.org/repos/asf/calcite/commit/01d4760c. Thanks for the
PR, [~kabhwan]!
was (Author: julianhyde):
Fixed in http://git-wip-us.apache.org/repos/asf/calcite/commit/80240720, with a
small fix-up in http://git-wip-us.apache.org/repos/asf/calcite/commit/01d4760c.
> Support ANY type with binary compare / arithmetic operators
> -----------------------------------------------------------
>
> Key: CALCITE-1453
> URL: https://issues.apache.org/jira/browse/CALCITE-1453
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Jungtaek Lim
> Assignee: Jungtaek Lim
> Fix For: 1.11.0
>
>
> Currently Calcite doesn't support applying binary compare / arithmetic
> operators with ANY type. One of example is
> CollectionTypeTest.testAccessNestedMapWithAnyTypeWithoutCast(). Without
> explicit casting, it can't find the matching backup method, and complaining
> there's no SqlFunctions.eq(Object, int).
> There seems to several ways to resolve this, but at least we don't want to
> make operator backup method for every combination of types. Needs to avoid
> this approach.
> When we're addressing this by having backup method, since we don't know the
> runtime type for ANY type, even if we succeed to call backup method with
> (Object, Object) parameters, two types can be different. This is OK for other
> types, but not Number types. This should be well cared, too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
