You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/03/15 19:17:33 UTC
[jira] [Commented] (HBASE-15279) OrderedBytes.isEncodedValue does
not check for int8 and int16 types
[ https://issues.apache.org/jira/browse/HBASE-15279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195853#comment-15195853 ]
Hudson commented on HBASE-15279:
--------------------------------
FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #1185 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1185/])
HBASE-15279 OrderedBytes.isEncodedValue does not check for int8 and (apurtell: rev b248751b75fa12958e82b1d4990c34f11ab45860)
* hbase-common/src/test/java/org/apache/hadoop/hbase/util/TestOrderedBytes.java
* hbase-common/src/main/java/org/apache/hadoop/hbase/util/OrderedBytes.java
> OrderedBytes.isEncodedValue does not check for int8 and int16 types
> -------------------------------------------------------------------
>
> Key: HBASE-15279
> URL: https://issues.apache.org/jira/browse/HBASE-15279
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.0.0, 1.3.0, 1.1.3
> Reporter: Robert Yokota
> Assignee: Robert Yokota
> Fix For: 2.0.0, 1.2.0, 1.3.0, 1.1.4, 0.98.18
>
> Attachments: HBASE-15279-2.patch, HBASE-15279.patch
>
>
> OrderedBytes.isEncodedValue does not check for int8 and int16 types. This also means that OrderedBytes.length may return an incorrect result, since it calls OrderedBytes.isEncodedValue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)