[
https://issues.apache.org/jira/browse/PHOENIX-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243733#comment-17243733
]
ASF GitHub Bot commented on PHOENIX-6241:
-----------------------------------------
yanxinyi opened a new pull request #1004:
URL: https://github.com/apache/phoenix/pull/1004
…re-4.15 version
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> ViewIndexId sequences collide with ones created on the pre-4.15 version
> -----------------------------------------------------------------------
>
> Key: PHOENIX-6241
> URL: https://issues.apache.org/jira/browse/PHOENIX-6241
> Project: Phoenix
> Issue Type: Bug
> Reporter: Xinyi Yan
> Assignee: Xinyi Yan
> Priority: Blocker
> Fix For: 4.16.0
>
>
> Start with 4.14 server and 4.14 client, create a table with PK (TENANT_ID,
> ID), create a global views with PK (A,B) and ID='firstView', and then create
> an index on firstView (a,b).
> Upgrade to the current 4.x branch server and client jar, create another
> global view with the same PK(A,B) but id = 'secondView', and then create an
> index on secondView(a,b).
> The sequence table created 2 rows and saw the sequence id collision(both of
> them have viewIndexid as SHORT.MIN_VALUE). This will cause index table data
> collisions because the index table starts with viewIndexId and tenantId in
> this case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
