[
https://issues.apache.org/jira/browse/HBASE-15333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273165#comment-15273165
]
Ted Yu commented on HBASE-15333:
--------------------------------
{code}
[INFO] # There is insufficient memory for the Java Runtime Environment to
continue.
[INFO] # Cannot create GC thread. Out of system resources.
[ERROR] # An error report file with more information is saved as:
[INFO] #
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/hbase-spark/hs_err_pid24147.log
{code}
Looks like build environment issue.
> 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,
> HBASE-15333-6.patch, HBASE-15333-7.patch, HBASE-15333-8.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)
