phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4514) A incorrect key object is used in SequenceManager#validateSequences
Date Fri, 12 Jan 2018 02:13:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16323427#comment-16323427
] 

Hudson commented on PHOENIX-4514:
---------------------------------

SUCCESS: Integrated in Jenkins build Phoenix-master #1912 (See [https://builds.apache.org/job/Phoenix-master/1912/])
PHOENIX-4514 A incorrect key object is used in (jtaylor: rev 83adf0d1a6e75c97f8ed696340c7af167834f7e9)
* (edit) phoenix-core/src/main/java/org/apache/phoenix/compile/SequenceManager.java


> A incorrect key object is used in SequenceManager#validateSequences
> -------------------------------------------------------------------
>
>                 Key: PHOENIX-4514
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4514
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>            Priority: Minor
>             Fix For: 5.0.0, 4.14.0, 4.13.2-cdh5.11.2
>
>         Attachments: PHOENIX.4514.v0.patch
>
>
> nextSequences.get( i ) -> nextSequences.get( i ).getSequenceKey()
> {code:title=SequenceManager.java}
>         for (int i = 0; i < nextSequences.size(); i++) {
>             sequencePosition[i] = sequenceMap.get(nextSequences.get(i)).getIndex();
>         }
> {code}
> It won't cause bug since the impl of SequenceAllocation#hashCode is equal with SequenceKey#hashCode.
However, it still a potential bug so a fix is necessary I believe.
> {code:title=SequenceAllocation.java}
>     @Override
>     public int hashCode() {
>         return sequenceKey.hashCode();
>     }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message