hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15279) OrderedBytes.isEncodedValue does not check for int8 and int16 types
Date Thu, 18 Feb 2016 10:57:18 GMT

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

Hudson commented on HBASE-15279:
--------------------------------

FAILURE: Integrated in HBase-1.3 #558 (See [https://builds.apache.org/job/HBase-1.3/558/])
HBASE-15279 OrderedBytes.isEncodedValue does not check for int8 and (stack: rev 5e7fecc15b366510a69f5479e8af13d1613ccc02)
* 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: 1.2.0
>
>         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)

Mime
View raw message