You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Saurabh Seth (JIRA)" <ji...@apache.org> on 2016/08/09 04:41:20 UTC
[jira] [Updated] (PHOENIX-2944) DATE Comparison Broken
[ https://issues.apache.org/jira/browse/PHOENIX-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Saurabh Seth updated PHOENIX-2944:
----------------------------------
Attachment: PHOENIX-2944.patch
I want to contribute to Phoenix and took a look at this issue just to get started. The issue here is with the compareTo methods in PDate and PTimestamp classes which are used during literal value comparisons.
I am attaching a patch with the fix and a few additional unit tests.
> DATE Comparison Broken
> ----------------------
>
> Key: PHOENIX-2944
> URL: https://issues.apache.org/jira/browse/PHOENIX-2944
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.7.0
> Reporter: Aaron Stephens
> Priority: Critical
> Labels: Phoenix
> Attachments: PHOENIX-2944.patch
>
>
> It appears that comparisons involving the DATE type are broken. See examples below:
> {noformat}
> > select DATE '2016-05-10 00:00:00' > DATE '2016-05-11 00:00:00';
> +-------+
> | true |
> +-------+
> | true |
> +-------+
> 1 row selected (0.001 seconds)
> > select TIMESTAMP '2016-05-10 00:00:00' > DATE '2016-05-11 00:00:00';
> +-------+
> | true |
> +-------+
> | true |
> +-------+
> 1 row selected (0.001 seconds)
> > select DATE '2016-05-10 00:00:00' > TIMESTAMP '2016-05-11 00:00:00';
> +-------+
> | true |
> +-------+
> | true |
> +-------+
> 1 row selected (0.001 seconds)
> > select TIMESTAMP '2016-05-10 00:00:00' > TIMESTAMP '2016-05-11 00:00:00';
> +--------+
> | false |
> +--------+
> | false |
> +--------+
> 1 row selected (0.001 seconds)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)