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

Posted to issues@calcite.apache.org by "Juhwan Kim (JIRA)" <ji...@apache.org> on 2019/05/22 17:45:00 UTC

[jira] [Comment Edited] (CALCITE-2829) Use consistent types when processing ranges

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

Juhwan Kim edited comment on CALCITE-2829 at 5/22/19 5:44 PM:
--------------------------------------------------------------

Thanks [~julianhyde]. I accidentally closed the previous PR while resolving merge conflict. Opened a new PR ([https://github.com/apache/calcite/pull/1227)] and updated commit message.


was (Author: juhwan):
Thanks for the suggestion. I accidentally closed the previous PR while resolving merge conflict. Opened a new PR ([https://github.com/apache/calcite/pull/1227)] and updated commit message.

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