[ 
https://issues.apache.org/jira/browse/CALCITE-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845645#comment-16845645
 ] 

Julian Hyde commented on CALCITE-2829:
--------------------------------------

Let’s start off with a good Jira case title and commit message. 

> 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: 50m
>  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)

Reply via email to