You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2015/08/02 21:57:04 UTC
[jira] [Updated] (PHOENIX-2137) Range query on DECIMAL DESC
sometimes incorrect
[ https://issues.apache.org/jira/browse/PHOENIX-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor updated PHOENIX-2137:
----------------------------------
Attachment: PHOENIX-2137_wip.patch
Parking patch with working unit tests. Needs one more review and a few comments.
> Range query on DECIMAL DESC sometimes incorrect
> -----------------------------------------------
>
> Key: PHOENIX-2137
> URL: https://issues.apache.org/jira/browse/PHOENIX-2137
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: James Taylor
> Attachments: PHOENIX-2137_wip.patch
>
>
> The following scenario is not working correctly:
> {code}
> create table t (k1 bigint not null, k2 decimal, constraint pk primary key (k1,k2 desc));
> upsert into t values(1,1.01);
> upsert into t values(2,1.001);
> select * from t where k2>1.0; -- No rows, but should be both rows
> select * from t where k1 in (1,2) and k2>1.0; -- Same problem
> {code}
> The following queries do return the correct results:
> {code}
> select * from t where k2>1.0001;
> select * from t where k1 in (1,2) and k2>1.0001;
> {code}
> Note also that without the DESC declaration of k2, everything works fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)