[
https://issues.apache.org/jira/browse/HBASE-13634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anoop Sam John updated HBASE-13634:
-----------------------------------
Summary: Avoid unsafe reference equality checks to EMPTY byte[] (was:
Unsafe reference equality checks to EMPTY_START_ROW)
> 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
> 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)
