[
https://issues.apache.org/jira/browse/CALCITE-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858092#comment-16858092
]
Juhwan Kim commented on CALCITE-2829:
-------------------------------------
[~danny0405]. I agree with your comment. Implicit type conversion would fix
this issue, and I also think that it is a much better idea. I uploaded my PR
with a simple test case. Do you mind adding that to your PR? Then, I think we
could resolve this ticket along with CALCITE-2302.
> Use consistent types when processing ranges
> -------------------------------------------
>
> 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: 1h
> 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)
