[jira] [Commented] (HBASE-19377) Compatibility checker complaining about hash collisions
[
https://issues.apache.org/jira/browse/HBASE-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511667#comment-16511667
]
Hudson commented on HBASE-19377:
Results for branch branch-1.2
[build #364 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/364/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/364//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/364//JDK7_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/364//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Compatibility checker complaining about hash collisions
>
>
> Key: HBASE-19377
> URL: https://issues.apache.org/jira/browse/HBASE-19377
> Project: HBase
> Issue Type: Bug
> Components: community
>Reporter: Andrew Purtell
>Assignee: Mike Drob
>Priority: Major
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.3.3, 2.0.1, 1.4.6
>
> Attachments: HBASE-19377.patch, HBASE-19377.v2.patch
>
>
> Had the compatibility checker complain about a hash collision. This fixed it:
> {code}
> --- java-acc/modules/Internals/Basic.pm.old 2017-11-29 11:50:41.0
> -0800
> +++ java-acc/modules/Internals/Basic.pm 2017-11-29 11:07:26.0
> -0800
> @@ -25,7 +25,7 @@
>
> my %Cache;
>
> -my $MD5_LEN = 8;
> +my $MD5_LEN = 10;
>
> sub getOSgroup()
> {
> {code}
> Not sure how best to fix this. Upstream PR? Patch locally?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19377) Compatibility checker complaining about hash collisions
[
https://issues.apache.org/jira/browse/HBASE-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511630#comment-16511630
]
Hudson commented on HBASE-19377:
Results for branch branch-1.4
[build #353 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/353/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/353//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/353//JDK7_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/353//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Compatibility checker complaining about hash collisions
>
>
> Key: HBASE-19377
> URL: https://issues.apache.org/jira/browse/HBASE-19377
> Project: HBase
> Issue Type: Bug
> Components: community
>Reporter: Andrew Purtell
>Assignee: Mike Drob
>Priority: Major
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.3.3, 2.0.1, 1.4.6
>
> Attachments: HBASE-19377.patch, HBASE-19377.v2.patch
>
>
> Had the compatibility checker complain about a hash collision. This fixed it:
> {code}
> --- java-acc/modules/Internals/Basic.pm.old 2017-11-29 11:50:41.0
> -0800
> +++ java-acc/modules/Internals/Basic.pm 2017-11-29 11:07:26.0
> -0800
> @@ -25,7 +25,7 @@
>
> my %Cache;
>
> -my $MD5_LEN = 8;
> +my $MD5_LEN = 10;
>
> sub getOSgroup()
> {
> {code}
> Not sure how best to fix this. Upstream PR? Patch locally?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19377) Compatibility checker complaining about hash collisions
[
https://issues.apache.org/jira/browse/HBASE-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511220#comment-16511220
]
Hudson commented on HBASE-19377:
Results for branch master
[build #364 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/364/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/364//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/364//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/364//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Compatibility checker complaining about hash collisions
>
>
> Key: HBASE-19377
> URL: https://issues.apache.org/jira/browse/HBASE-19377
> Project: HBase
> Issue Type: Bug
> Components: community
>Reporter: Andrew Purtell
>Assignee: Mike Drob
>Priority: Major
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.3.3, 2.0.1, 1.4.6
>
> Attachments: HBASE-19377.patch, HBASE-19377.v2.patch
>
>
> Had the compatibility checker complain about a hash collision. This fixed it:
> {code}
> --- java-acc/modules/Internals/Basic.pm.old 2017-11-29 11:50:41.0
> -0800
> +++ java-acc/modules/Internals/Basic.pm 2017-11-29 11:07:26.0
> -0800
> @@ -25,7 +25,7 @@
>
> my %Cache;
>
> -my $MD5_LEN = 8;
> +my $MD5_LEN = 10;
>
> sub getOSgroup()
> {
> {code}
> Not sure how best to fix this. Upstream PR? Patch locally?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19377) Compatibility checker complaining about hash collisions
[
https://issues.apache.org/jira/browse/HBASE-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510920#comment-16510920
]
Hudson commented on HBASE-19377:
Results for branch branch-1
[build #347 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/347/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/347//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/347//JDK7_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/347//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
> Compatibility checker complaining about hash collisions
>
>
> Key: HBASE-19377
> URL: https://issues.apache.org/jira/browse/HBASE-19377
> Project: HBase
> Issue Type: Bug
> Components: community
>Reporter: Andrew Purtell
>Assignee: Mike Drob
>Priority: Major
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.3.3, 2.0.1, 1.4.6
>
> Attachments: HBASE-19377.patch, HBASE-19377.v2.patch
>
>
> Had the compatibility checker complain about a hash collision. This fixed it:
> {code}
> --- java-acc/modules/Internals/Basic.pm.old 2017-11-29 11:50:41.0
> -0800
> +++ java-acc/modules/Internals/Basic.pm 2017-11-29 11:07:26.0
> -0800
> @@ -25,7 +25,7 @@
>
> my %Cache;
>
> -my $MD5_LEN = 8;
> +my $MD5_LEN = 10;
>
> sub getOSgroup()
> {
> {code}
> Not sure how best to fix this. Upstream PR? Patch locally?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19377) Compatibility checker complaining about hash collisions
[
https://issues.apache.org/jira/browse/HBASE-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510641#comment-16510641
]
Hudson commented on HBASE-19377:
Results for branch branch-2
[build #856 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/856/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/856//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/856//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/856//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Compatibility checker complaining about hash collisions
>
>
> Key: HBASE-19377
> URL: https://issues.apache.org/jira/browse/HBASE-19377
> Project: HBase
> Issue Type: Bug
> Components: community
>Reporter: Andrew Purtell
>Assignee: Mike Drob
>Priority: Major
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.3.3, 2.0.1, 1.4.6
>
> Attachments: HBASE-19377.patch, HBASE-19377.v2.patch
>
>
> Had the compatibility checker complain about a hash collision. This fixed it:
> {code}
> --- java-acc/modules/Internals/Basic.pm.old 2017-11-29 11:50:41.0
> -0800
> +++ java-acc/modules/Internals/Basic.pm 2017-11-29 11:07:26.0
> -0800
> @@ -25,7 +25,7 @@
>
> my %Cache;
>
> -my $MD5_LEN = 8;
> +my $MD5_LEN = 10;
>
> sub getOSgroup()
> {
> {code}
> Not sure how best to fix this. Upstream PR? Patch locally?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19377) Compatibility checker complaining about hash collisions
[
https://issues.apache.org/jira/browse/HBASE-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510603#comment-16510603
]
Hudson commented on HBASE-19377:
Results for branch branch-2.0
[build #422 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/422/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/422//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/422//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/422//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Compatibility checker complaining about hash collisions
>
>
> Key: HBASE-19377
> URL: https://issues.apache.org/jira/browse/HBASE-19377
> Project: HBase
> Issue Type: Bug
> Components: community
>Reporter: Andrew Purtell
>Assignee: Mike Drob
>Priority: Major
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.3.3, 2.0.1, 1.4.6
>
> Attachments: HBASE-19377.patch, HBASE-19377.v2.patch
>
>
> Had the compatibility checker complain about a hash collision. This fixed it:
> {code}
> --- java-acc/modules/Internals/Basic.pm.old 2017-11-29 11:50:41.0
> -0800
> +++ java-acc/modules/Internals/Basic.pm 2017-11-29 11:07:26.0
> -0800
> @@ -25,7 +25,7 @@
>
> my %Cache;
>
> -my $MD5_LEN = 8;
> +my $MD5_LEN = 10;
>
> sub getOSgroup()
> {
> {code}
> Not sure how best to fix this. Upstream PR? Patch locally?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19377) Compatibility checker complaining about hash collisions
[
https://issues.apache.org/jira/browse/HBASE-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510399#comment-16510399
]
Hudson commented on HBASE-19377:
Results for branch branch-1.3
[build #359 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/359/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/359//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/359//JDK7_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/359//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Compatibility checker complaining about hash collisions
>
>
> Key: HBASE-19377
> URL: https://issues.apache.org/jira/browse/HBASE-19377
> Project: HBase
> Issue Type: Bug
> Components: community
>Reporter: Andrew Purtell
>Assignee: Mike Drob
>Priority: Major
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.3.3, 2.0.1, 1.4.6
>
> Attachments: HBASE-19377.patch, HBASE-19377.v2.patch
>
>
> Had the compatibility checker complain about a hash collision. This fixed it:
> {code}
> --- java-acc/modules/Internals/Basic.pm.old 2017-11-29 11:50:41.0
> -0800
> +++ java-acc/modules/Internals/Basic.pm 2017-11-29 11:07:26.0
> -0800
> @@ -25,7 +25,7 @@
>
> my %Cache;
>
> -my $MD5_LEN = 8;
> +my $MD5_LEN = 10;
>
> sub getOSgroup()
> {
> {code}
> Not sure how best to fix this. Upstream PR? Patch locally?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19377) Compatibility checker complaining about hash collisions
[
https://issues.apache.org/jira/browse/HBASE-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510175#comment-16510175
]
Hudson commented on HBASE-19377:
SUCCESS: Integrated in Jenkins build HBase-1.2-IT #1123 (See
[https://builds.apache.org/job/HBase-1.2-IT/1123/])
HBASE-19377 Update Java API CC version (mdrob: rev
595307f258338cedab4304b78af111376e656ff3)
* (edit) dev-support/checkcompatibility.py
> Compatibility checker complaining about hash collisions
>
>
> Key: HBASE-19377
> URL: https://issues.apache.org/jira/browse/HBASE-19377
> Project: HBase
> Issue Type: Bug
> Components: community
>Reporter: Andrew Purtell
>Assignee: Mike Drob
>Priority: Major
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.3.3, 2.0.1, 1.4.6
>
> Attachments: HBASE-19377.patch, HBASE-19377.v2.patch
>
>
> Had the compatibility checker complain about a hash collision. This fixed it:
> {code}
> --- java-acc/modules/Internals/Basic.pm.old 2017-11-29 11:50:41.0
> -0800
> +++ java-acc/modules/Internals/Basic.pm 2017-11-29 11:07:26.0
> -0800
> @@ -25,7 +25,7 @@
>
> my %Cache;
>
> -my $MD5_LEN = 8;
> +my $MD5_LEN = 10;
>
> sub getOSgroup()
> {
> {code}
> Not sure how best to fix this. Upstream PR? Patch locally?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19377) Compatibility checker complaining about hash collisions
[
https://issues.apache.org/jira/browse/HBASE-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510168#comment-16510168
]
Hudson commented on HBASE-19377:
SUCCESS: Integrated in Jenkins build HBase-1.3-IT #422 (See
[https://builds.apache.org/job/HBase-1.3-IT/422/])
HBASE-19377 Update Java API CC version (mdrob: rev
7d51f6077b7ccd33293f8bca4ae4e8958b4b7952)
* (edit) dev-support/checkcompatibility.py
> Compatibility checker complaining about hash collisions
>
>
> Key: HBASE-19377
> URL: https://issues.apache.org/jira/browse/HBASE-19377
> Project: HBase
> Issue Type: Bug
> Components: community
>Reporter: Andrew Purtell
>Assignee: Mike Drob
>Priority: Major
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.3.3, 2.0.1, 1.4.6
>
> Attachments: HBASE-19377.patch, HBASE-19377.v2.patch
>
>
> Had the compatibility checker complain about a hash collision. This fixed it:
> {code}
> --- java-acc/modules/Internals/Basic.pm.old 2017-11-29 11:50:41.0
> -0800
> +++ java-acc/modules/Internals/Basic.pm 2017-11-29 11:07:26.0
> -0800
> @@ -25,7 +25,7 @@
>
> my %Cache;
>
> -my $MD5_LEN = 8;
> +my $MD5_LEN = 10;
>
> sub getOSgroup()
> {
> {code}
> Not sure how best to fix this. Upstream PR? Patch locally?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19377) Compatibility checker complaining about hash collisions
[
https://issues.apache.org/jira/browse/HBASE-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510142#comment-16510142
]
stack commented on HBASE-19377:
---
+1. I thought I'd updated the checkcompatibility but doesn't look like it. Nice
fix.
> Compatibility checker complaining about hash collisions
>
>
> Key: HBASE-19377
> URL: https://issues.apache.org/jira/browse/HBASE-19377
> Project: HBase
> Issue Type: Bug
> Components: community
>Reporter: Andrew Purtell
>Assignee: Mike Drob
>Priority: Major
> Attachments: HBASE-19377.patch, HBASE-19377.v2.patch
>
>
> Had the compatibility checker complain about a hash collision. This fixed it:
> {code}
> --- java-acc/modules/Internals/Basic.pm.old 2017-11-29 11:50:41.0
> -0800
> +++ java-acc/modules/Internals/Basic.pm 2017-11-29 11:07:26.0
> -0800
> @@ -25,7 +25,7 @@
>
> my %Cache;
>
> -my $MD5_LEN = 8;
> +my $MD5_LEN = 10;
>
> sub getOSgroup()
> {
> {code}
> Not sure how best to fix this. Upstream PR? Patch locally?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19377) Compatibility checker complaining about hash collisions
[
https://issues.apache.org/jira/browse/HBASE-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510138#comment-16510138
]
Sean Busbey commented on HBASE-19377:
-
+1 on v2
> Compatibility checker complaining about hash collisions
>
>
> Key: HBASE-19377
> URL: https://issues.apache.org/jira/browse/HBASE-19377
> Project: HBase
> Issue Type: Bug
> Components: community
>Reporter: Andrew Purtell
>Assignee: Mike Drob
>Priority: Major
> Attachments: HBASE-19377.patch, HBASE-19377.v2.patch
>
>
> Had the compatibility checker complain about a hash collision. This fixed it:
> {code}
> --- java-acc/modules/Internals/Basic.pm.old 2017-11-29 11:50:41.0
> -0800
> +++ java-acc/modules/Internals/Basic.pm 2017-11-29 11:07:26.0
> -0800
> @@ -25,7 +25,7 @@
>
> my %Cache;
>
> -my $MD5_LEN = 8;
> +my $MD5_LEN = 10;
>
> sub getOSgroup()
> {
> {code}
> Not sure how best to fix this. Upstream PR? Patch locally?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19377) Compatibility checker complaining about hash collisions
[
https://issues.apache.org/jira/browse/HBASE-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510131#comment-16510131
]
Hadoop QA commented on HBASE-19377:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
13s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} pylint {color} | {color:green} 0m
6s{color} | {color:green} There were no new pylint issues. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
13s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 0m 44s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:b002b0b |
| JIRA Issue | HBASE-19377 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12927527/HBASE-19377.v2.patch |
| Optional Tests | asflicense pylint |
| uname | Linux 55e0259695c1 3.13.0-139-generic #188-Ubuntu SMP Tue Jan 9
14:43:09 UTC 2018 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / edf60b965b |
| maven | version: Apache Maven 3.5.3
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z) |
| pylint | v1.6.5 |
| Max. process+thread count | 43 (vs. ulimit of 1) |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/13212/console |
| Powered by | Apache Yetus 0.7.0 http://yetus.apache.org |
This message was automatically generated.
> Compatibility checker complaining about hash collisions
>
>
> Key: HBASE-19377
> URL: https://issues.apache.org/jira/browse/HBASE-19377
> Project: HBase
> Issue Type: Bug
> Components: community
>Reporter: Andrew Purtell
>Assignee: Mike Drob
>Priority: Major
> Attachments: HBASE-19377.patch, HBASE-19377.v2.patch
>
>
> Had the compatibility checker complain about a hash collision. This fixed it:
> {code}
> --- java-acc/modules/Internals/Basic.pm.old 2017-11-29 11:50:41.0
> -0800
> +++ java-acc/modules/Internals/Basic.pm 2017-11-29 11:07:26.0
> -0800
> @@ -25,7 +25,7 @@
>
> my %Cache;
>
> -my $MD5_LEN = 8;
> +my $MD5_LEN = 10;
>
> sub getOSgroup()
> {
> {code}
> Not sure how best to fix this. Upstream PR? Patch locally?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19377) Compatibility checker complaining about hash collisions
[
https://issues.apache.org/jira/browse/HBASE-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510102#comment-16510102
]
Mike Drob commented on HBASE-19377:
---
v2: collapse version logging to single line
> Compatibility checker complaining about hash collisions
>
>
> Key: HBASE-19377
> URL: https://issues.apache.org/jira/browse/HBASE-19377
> Project: HBase
> Issue Type: Bug
> Components: community
>Reporter: Andrew Purtell
>Assignee: Mike Drob
>Priority: Major
> Attachments: HBASE-19377.patch, HBASE-19377.v2.patch
>
>
> Had the compatibility checker complain about a hash collision. This fixed it:
> {code}
> --- java-acc/modules/Internals/Basic.pm.old 2017-11-29 11:50:41.0
> -0800
> +++ java-acc/modules/Internals/Basic.pm 2017-11-29 11:07:26.0
> -0800
> @@ -25,7 +25,7 @@
>
> my %Cache;
>
> -my $MD5_LEN = 8;
> +my $MD5_LEN = 10;
>
> sub getOSgroup()
> {
> {code}
> Not sure how best to fix this. Upstream PR? Patch locally?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19377) Compatibility checker complaining about hash collisions
[
https://issues.apache.org/jira/browse/HBASE-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510041#comment-16510041
]
Hadoop QA commented on HBASE-19377:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
23s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} pylint {color} | {color:green} 0m
6s{color} | {color:green} There were no new pylint issues. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
18s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 1m 2s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:b002b0b |
| JIRA Issue | HBASE-19377 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12927517/HBASE-19377.patch |
| Optional Tests | asflicense pylint |
| uname | Linux 857ddc7b4f53 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10
14:24:03 UTC 2017 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / edf60b965b |
| maven | version: Apache Maven 3.5.3
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z) |
| pylint | v1.6.5 |
| Max. process+thread count | 48 (vs. ulimit of 1) |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/13210/console |
| Powered by | Apache Yetus 0.7.0 http://yetus.apache.org |
This message was automatically generated.
> Compatibility checker complaining about hash collisions
>
>
> Key: HBASE-19377
> URL: https://issues.apache.org/jira/browse/HBASE-19377
> Project: HBase
> Issue Type: Bug
> Components: community
>Reporter: Andrew Purtell
>Assignee: Mike Drob
>Priority: Major
> Attachments: HBASE-19377.patch
>
>
> Had the compatibility checker complain about a hash collision. This fixed it:
> {code}
> --- java-acc/modules/Internals/Basic.pm.old 2017-11-29 11:50:41.0
> -0800
> +++ java-acc/modules/Internals/Basic.pm 2017-11-29 11:07:26.0
> -0800
> @@ -25,7 +25,7 @@
>
> my %Cache;
>
> -my $MD5_LEN = 8;
> +my $MD5_LEN = 10;
>
> sub getOSgroup()
> {
> {code}
> Not sure how best to fix this. Upstream PR? Patch locally?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19377) Compatibility checker complaining about hash collisions
[
https://issues.apache.org/jira/browse/HBASE-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271826#comment-16271826
]
Appy commented on HBASE-19377:
--
Looking at this commit, looks like it was increased in recent releases.
Commit:
https://github.com/lvc/japi-compliance-checker/commit/9d78fb028752b905326eb67f9748ff1646102746
First release with that change:
https://github.com/lvc/japi-compliance-checker/releases/tag/2.2
> Compatibility checker complaining about hash collisions
>
>
> Key: HBASE-19377
> URL: https://issues.apache.org/jira/browse/HBASE-19377
> Project: HBase
> Issue Type: Bug
>Reporter: Andrew Purtell
>
> Had the compatibility checker complain about a hash collision. This fixed it:
> {code}
> --- java-acc/modules/Internals/Basic.pm.old 2017-11-29 11:50:41.0
> -0800
> +++ java-acc/modules/Internals/Basic.pm 2017-11-29 11:07:26.0
> -0800
> @@ -25,7 +25,7 @@
>
> my %Cache;
>
> -my $MD5_LEN = 8;
> +my $MD5_LEN = 10;
>
> sub getOSgroup()
> {
> {code}
> Not sure how best to fix this. Upstream PR? Patch locally?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19377) Compatibility checker complaining about hash collisions
[
https://issues.apache.org/jira/browse/HBASE-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271816#comment-16271816
]
Sean Busbey commented on HBASE-19377:
-
I'd recommend PR upstream. The maintainer has historically been responsive.
> Compatibility checker complaining about hash collisions
>
>
> Key: HBASE-19377
> URL: https://issues.apache.org/jira/browse/HBASE-19377
> Project: HBase
> Issue Type: Bug
>Reporter: Andrew Purtell
>
> Had the compatibility checker complain about a hash collision. This fixed it:
> {code}
> --- java-acc/modules/Internals/Basic.pm.old 2017-11-29 11:50:41.0
> -0800
> +++ java-acc/modules/Internals/Basic.pm 2017-11-29 11:07:26.0
> -0800
> @@ -25,7 +25,7 @@
>
> my %Cache;
>
> -my $MD5_LEN = 8;
> +my $MD5_LEN = 10;
>
> sub getOSgroup()
> {
> {code}
> Not sure how best to fix this. Upstream PR? Patch locally?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19377) Compatibility checker complaining about hash collisions
[
https://issues.apache.org/jira/browse/HBASE-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271618#comment-16271618
]
Andrew Purtell commented on HBASE-19377:
bq. What does the hash collision complain look like?
{noformat}
ERROR: md5 collision on '2f0124d1', please increase ID length (MD5_LEN in
Basic.pm)
{noformat}
> Compatibility checker complaining about hash collisions
>
>
> Key: HBASE-19377
> URL: https://issues.apache.org/jira/browse/HBASE-19377
> Project: HBase
> Issue Type: Bug
>Reporter: Andrew Purtell
>
> Had the compatibility checker complain about a hash collision. This fixed it:
> {code}
> --- java-acc/modules/Internals/Basic.pm.old 2017-11-29 11:50:41.0
> -0800
> +++ java-acc/modules/Internals/Basic.pm 2017-11-29 11:07:26.0
> -0800
> @@ -25,7 +25,7 @@
>
> my %Cache;
>
> -my $MD5_LEN = 8;
> +my $MD5_LEN = 10;
>
> sub getOSgroup()
> {
> {code}
> Not sure how best to fix this. Upstream PR? Patch locally?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19377) Compatibility checker complaining about hash collisions
[
https://issues.apache.org/jira/browse/HBASE-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271566#comment-16271566
]
Appy commented on HBASE-19377:
--
Maybe send a note to dev so other who stumble on same thing know this?
What does the hash collision complain look like?
> Compatibility checker complaining about hash collisions
>
>
> Key: HBASE-19377
> URL: https://issues.apache.org/jira/browse/HBASE-19377
> Project: HBase
> Issue Type: Bug
>Reporter: Andrew Purtell
>
> A sufficiently complex git repo will have the compatibility checker
> complaining about hash collisions. This will fix it:
> {code}
> --- java-acc/modules/Internals/Basic.pm.old 2017-11-29 11:50:41.0
> -0800
> +++ java-acc/modules/Internals/Basic.pm 2017-11-29 11:07:26.0
> -0800
> @@ -25,7 +25,7 @@
>
> my %Cache;
>
> -my $MD5_LEN = 8;
> +my $MD5_LEN = 10;
>
> sub getOSgroup()
> {
> {code}
> Not sure how best to fix this. Upstream PR? Patch locally?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
