[
https://issues.apache.org/jira/browse/CALCITE-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16801822#comment-16801822
]
Zoltan Haindrich commented on CALCITE-2829:
-------------------------------------------
[~Juhwan] I understand that this issue surfaces during simplification; but I
feel that the fix shouldn't reside in "simplifyComparision" as I would guess
that the issue might arise elsewhere as well..
instead; I would expect that this should be fixed where the "comparison" node
is constructed (right now I would guess some RexBuilder part ; but I could be
easily wrong)
> Fix RexSimplify#processRange cast issue
> ---------------------------------------
>
> Key: CALCITE-2829
> URL: https://issues.apache.org/jira/browse/CALCITE-2829
> Project: Calcite
> Issue Type: Bug
> Reporter: Siddharth Teotia
> Assignee: Juhwan Kim
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Range expressions like <ts> = 'literal' AND <ts> < 'literal' trigger
> ClassCastException as literal are implicitly casted differently between =/<>
> operators and other comparison operators. Apply the same casting rules for
> comparison to =/<> calls when processing ranges, so that all the terms have
> the same type for literals.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
