[
https://issues.apache.org/jira/browse/HBASE-26276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413107#comment-17413107
]
Wellington Chevreuil commented on HBASE-26276:
----------------------------------------------
Ain't sure why PR didn't link automatically:
https://github.com/apache/hbase/pull/3673
> Allow HashTable/SyncTable to perform rawScan when comparing cells
> -----------------------------------------------------------------
>
> Key: HBASE-26276
> URL: https://issues.apache.org/jira/browse/HBASE-26276
> Project: HBase
> Issue Type: Improvement
> Reporter: Wellington Chevreuil
> Assignee: Wellington Chevreuil
> Priority: Major
>
> We had noticed some of our customers having inconsistent results when running
> HashTable/SyncTable in scenarios described previously by HBASE-21596. As
> discussed on HBASE-21596, one alternative to avoid such inconsistencies, is
> to set 'NEW_VERSION_BEHAVIOUR' introduced by HBASE-15968. That, however, does
> rely on the order of operations, which can't be guaranteed when standard
> replication (not serial replication) is being used, which is the case on the
> majority of our customers.
> A possible workaround is to place delete markers to every single cell version
> returned on a raw scan, and setting a high value to the scan number of
> versions to be read.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
