Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@phoenix.apache.org
Date: Tue, 11 Aug 2015 01:28:45 +0000 (UTC)
From: "James Taylor (JIRA)" <jira@apache.org>
To: dev@phoenix.incubator.apache.org
Message-ID: <JIRA.12846952.1437587080000.28044.1439256525733@Atlassian.JIRA>
In-Reply-To: <JIRA.12846952.1437587080000@Atlassian.JIRA>
References: <JIRA.12846952.1437587080000@Atlassian.JIRA>
 <JIRA.12846952.1437587080008@arcas>
Subject: [jira] [Updated] (PHOENIX-2137) Range query on DECIMAL DESC
 sometimes incorrect
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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_v2.patch

Final patch with more testing. Please review, [~samarthjain] - I'd like to get this into a patch release very soon so we can put these descending row key bugs behind us.

> 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.patch, PHOENIX-2137_v2.patch, 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)