hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhan Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15333) [hbase-spark] Enhance dataframe filters to handle naively encoded short, integer, long, float and double
Date Fri, 13 May 2016 21:02:13 GMT

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

Zhan Zhang commented on HBASE-15333:
------------------------------------

Not sure why it is not caught during the systest.  The failure happens only in test cases.
Will open a followup jira to fix the issue.

> [hbase-spark] Enhance dataframe filters to handle naively encoded short, integer, long,
float and double
> --------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-15333
>                 URL: https://issues.apache.org/jira/browse/HBASE-15333
>             Project: HBase
>          Issue Type: Sub-task
>          Components: spark
>            Reporter: Zhan Zhang
>            Assignee: Zhan Zhang
>             Fix For: 2.0.0
>
>         Attachments: HBASE-15333-1.patch, HBASE-15333-10.patch, HBASE-15333-2.patch,
HBASE-15333-3.patch, HBASE-15333-4.patch, HBASE-15333-5.patch, HBASE-15333-6.patch, HBASE-15333-7.patch,
HBASE-15333-8.patch, HBASE-15333-9.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)

Mime
View raw message