You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2015/05/07 15:42:00 UTC

[jira] [Assigned] (HBASE-13634) Avoid unsafe reference equality checks to EMPTY byte[]

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

Ted Yu reassigned HBASE-13634:
------------------------------

    Assignee: Lars Francke

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