[
https://issues.apache.org/jira/browse/PHOENIX-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243739#comment-17243739
]
ASF GitHub Bot commented on PHOENIX-6241:
-----------------------------------------
yanxinyi commented on pull request #1004:
URL: https://github.com/apache/phoenix/pull/1004#issuecomment-738587222
During the upgrade, we disallow certain operations, which results in the
query that returns an empty ResultSet from the sequence table(sequence table is
not empty). I'm sure that scn and atomic flag upgradeRequired make things diff
than the regular query connection. For this reason, I moved merge view index
id logic at the end of the upgradeSystemTables method. In addition, I also
added a MergeViewIndexIdSequencesTool that can run it separately to catch up
merge view index id logic later.
----------------------------------------------------------------
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)
