[
https://issues.apache.org/jira/browse/PHOENIX-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226761#comment-14226761
]
Hudson commented on PHOENIX-1472:
---------------------------------
SUCCESS: Integrated in Phoenix-3.0-hadoop1 #325 (See
[https://builds.apache.org/job/Phoenix-3.0-hadoop1/325/])
PHOENIX-1472 Fix salt bucket for Integer.MIN_VALUE (gabrielr: rev
40193187210329cb3c465e5d6cb33b197f50fe79)
* phoenix-core/src/test/java/org/apache/phoenix/schema/SaltingUtilTest.java
* phoenix-core/src/main/java/org/apache/phoenix/schema/SaltingUtil.java
> SaltingUtil calculates wrong salt key for Integer.MIN_VALUE hash code
> ---------------------------------------------------------------------
>
> Key: PHOENIX-1472
> URL: https://issues.apache.org/jira/browse/PHOENIX-1472
> Project: Phoenix
> Issue Type: Bug
> Reporter: Gabriel Reid
> Assignee: Gabriel Reid
> Fix For: 5.0.0, 4.3, 3.3, 3.2.2, 4.2.2
>
> Attachments: PHOENIX-1472.1.patch, PHOENIX-1472.patch
>
>
> There is an edge case in SaltingUtil.getSaltingByte where an invalid salt
> byte is calculated. This happens when the hash code of the row key being
> salted is equal to {{Integer.MIN_VALUE}}. The underlying bug is the use of
> Math.abs(hashCode) in SaltingUtil.getSaltingByte, and the result of the bug
> is that a hash code outside of the range of configured salt buckets can be
> returned.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
