[ 
https://issues.apache.org/jira/browse/HBASE-13634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack updated HBASE-13634:
--------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.1.1)
                       (was: 1.2.0)
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Pushed to master. If you have a patch for branch-1, I'll apply it here 
[~lars_francke] Thanks.

> 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)

Reply via email to