You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Stamatis Zampetakis (JIRA)" <ji...@apache.org> on 2019/02/14 22:04:00 UTC

[jira] [Commented] (CALCITE-2829) Fix RexSimplify#processRange cast issue

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

Stamatis Zampetakis commented on CALCITE-2829:
----------------------------------------------

Hi [~siddteotia], it seems you are describing a bug. Can you change the summary /description to better explain how and when it appears. If you have an SQL statement that fails it would be nice to include it also. 

> 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: Julian Hyde
>            Priority: Major
>
> 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)