phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-5138) ViewIndexId sequences created after PHOENIX-5132 shouldn't collide with ones created before it
Date Tue, 09 Apr 2019 20:42:00 GMT

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

Hudson commented on PHOENIX-5138:
---------------------------------

FAILURE: Integrated in Jenkins build PreCommit-PHOENIX-Build #2500 (See [https://builds.apache.org/job/PreCommit-PHOENIX-Build/2500/])
PHOENIX-5138 - ViewIndexId sequences created after PHOENIX-5132 (gjacoby: rev 6ca7ff61ca9d8d89343fb331aed25afe174c8ca5)
* (edit) phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataEndpointImpl.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/util/MetaDataUtil.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/util/UpgradeUtil.java
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/index/ViewIndexIT.java
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/UpgradeIT.java


> ViewIndexId sequences created after PHOENIX-5132 shouldn't collide with ones created
before it
> ----------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-5138
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5138
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.15.0, 5.1
>            Reporter: Geoffrey Jacoby
>            Assignee: Geoffrey Jacoby
>            Priority: Blocker
>             Fix For: 4.15.0, 5.1.0
>
>         Attachments: PHOENIX-5138-v2.patch, PHOENIX-5138-v3.patch, PHOENIX-5138-v4.patch,
PHOENIX-5138.patch
>
>          Time Spent: 4h 10m
>  Remaining Estimate: 0h
>
> PHOENIX-5132 changed the ViewIndexId generation logic to use one sequence per physical
view index table, whereas before it had been tenant + physical table. This removed the possibility
of a tenant view index and a global view index having colliding ViewIndexIds.
> However, existing Phoenix environments may have already created tenant-owned view index
ids using the old sequence, and under PHOENIX-5132 if they create another, its ViewIndexId
will got back to MIN_VALUE, which could cause a collision with an existing view index id.




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message