[
https://issues.apache.org/jira/browse/HBASE-13634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538616#comment-14538616
]
Hudson commented on HBASE-13634:
--------------------------------
FAILURE: Integrated in HBase-TRUNK #6473 (See
[https://builds.apache.org/job/HBase-TRUNK/6473/])
HBASE-13634 Avoid unsafe reference equality checks to EMPTY byte[] (stack: rev
fa6dc9c44e28aa608d5204db814e8442b95eb125)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/util/RegionSplitCalculator.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StripeStoreFileManager.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StripeMultiFileWriter.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ScanQueryMatcher.java
> Avoid unsafe reference equality checks to EMPTY byte[]
> ------------------------------------------------------
>
> Key: HBASE-13634
> URL: https://issues.apache.org/jira/browse/HBASE-13634
> Project: HBase
> Issue Type: Bug
> Components: Compaction, Scanners
> Reporter: Dave Latham
> Assignee: Lars Francke
> Fix For: 2.0.0
>
> Attachments: HBASE-13634-v1.patch, HBASE-13634.patch
>
>
> While looking to see if there was a standard method in the code base for
> testing for the empty start and end row, I noticed some cases that are using
> unsafe reference equality checks and thus may have incorrect behavior in
> boundary cases:
> ScanQueryMatcher.checkPartialDropDeleteRange
> StripeStoreFileManager.findStripeForRow
> It looks like both are intended to support stripe compaction
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
