[
https://issues.apache.org/jira/browse/HBASE-30159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18087844#comment-18087844
]
Hudson commented on HBASE-30159:
--------------------------------
Results for branch branch-2.6
[build #475 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/475/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/475/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/475/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/475/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/475/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/475/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
> Make hash algorithm configurable for HashTable/SyncTable
> --------------------------------------------------------
>
> Key: HBASE-30159
> URL: https://issues.apache.org/jira/browse/HBASE-30159
> Project: HBase
> Issue Type: Sub-task
> Reporter: Balazs Meszaros
> Assignee: JinHyuk Kim
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.5.16, 2.6.7
>
>
> The HashTable MapReduce job utilizes MD5 hashes to determine whether row data
> needs to be synchronized between source and target tables. However, because
> users can control all hash inputs (row, column family, column, value, and
> timestamp), a malicious user could intentionally trigger a collision by
> creating two distinct rows with identical hashes. This would result in less
> rows in the target table which is hard to find.
> We must make the hashing algorithm configurable to allow for more
> collision-resistant hash algorithms.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
