Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 30 Mar 2016 21:07:25 +0000 (UTC)
From: "Zhan Zhang (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12944692.1456441094000.93154.1459372045586@Atlassian.JIRA>
In-Reply-To: <JIRA.12944692.1456441094000@Atlassian.JIRA>
References: <JIRA.12944692.1456441094000@Atlassian.JIRA>
 <JIRA.12944692.1456441094325@arcas>
Subject: [jira] [Updated] (HBASE-15333) Enhance the filter to handle short,
 integer, long, float and double
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-15333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhan Zhang updated HBASE-15333:
-------------------------------
    Attachment: HBASE-15333-5.patch

> Enhance the filter to handle short, integer, long, float and double
> -------------------------------------------------------------------
>
>                 Key: HBASE-15333
>                 URL: https://issues.apache.org/jira/browse/HBASE-15333
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Zhan Zhang
>            Assignee: Zhan Zhang
>         Attachments: HBASE-15333-1.patch, HBASE-15333-2.patch, HBASE-15333-3.patch, HBASE-15333-4.patch, HBASE-15333-5.patch
>
>
> Currently, the range filter is based on the order of bytes. But for java primitive type, such as short, int, long, double, float, etc, their order is not consistent with their byte order, extra manipulation has to be in place to take care of them  correctly.
> For example, for the integer range (-100, 100), the filter <= 1, the current filter will return 0 and 1, and the right return value should be (-100, 1]


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)