Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.0.0-alpha-1, 2.2.7, 2.5.0, 2.3.6, 2.4.6
-
None
-
None
Description
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.
Attachments
Issue Links
- relates to
-
HBASE-21596 Delete for a specific cell version can bring back versions above VERSIONS limit
- Resolved
- links to