[
https://issues.apache.org/jira/browse/HBASE-26276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413454#comment-17413454
]
Hudson commented on HBASE-26276:
--------------------------------
Results for branch branch-2.4
[build #196 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/196/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/196/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/196/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/196/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/196/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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
> Affects Versions: 3.0.0-alpha-1, 2.5.0, 2.3.6, 2.4.6
> Reporter: Wellington Chevreuil
> Assignee: Wellington Chevreuil
> Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-2, 2.3.7, 2.4.7
>
>
> 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)
