You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Xinyi Yan (Jira)" <ji...@apache.org> on 2020/12/04 04:13:00 UTC

[jira] [Assigned] (PHOENIX-6241) ViewIndexId sequences collide with ones created on the pre-4.15 version

     [ https://issues.apache.org/jira/browse/PHOENIX-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xinyi Yan reassigned PHOENIX-6241:
----------------------------------

    Assignee: Xinyi Yan

> 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)