You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/04/05 23:46:00 UTC
[jira] [Commented] (HBASE-15333) [hbase-spark] Enhance dataframe
filters to handle naively encoded short, integer, long, float and double
[ https://issues.apache.org/jira/browse/HBASE-15333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427768#comment-16427768 ]
stack commented on HBASE-15333:
-------------------------------
Reverted from branch-2/2.0.0 by HBASE-18817
> [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
> Priority: Major
> Fix For: 3.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
(v7.6.3#76005)