[jira] [Updated] (PHOENIX-5138) ViewIndexId sequences created after PHOENIX-5132 shouldn't collide with ones created before it
[ https://issues.apache.org/jira/browse/PHOENIX-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5138: Fix Version/s: 5.0.1 > 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, 5.0.1 > > Attachments: PHOENIX-5138-v2.patch, PHOENIX-5138-v3.patch, > PHOENIX-5138-v4.patch, PHOENIX-5138.patch > > Time Spent: 4h 50m > 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)
[jira] [Updated] (PHOENIX-5138) ViewIndexId sequences created after PHOENIX-5132 shouldn't collide with ones created before it
[ https://issues.apache.org/jira/browse/PHOENIX-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Jacoby updated PHOENIX-5138: - Attachment: PHOENIX-5138-v4.patch > 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)
[jira] [Updated] (PHOENIX-5138) ViewIndexId sequences created after PHOENIX-5132 shouldn't collide with ones created before it
[ https://issues.apache.org/jira/browse/PHOENIX-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Jacoby updated PHOENIX-5138: - Attachment: PHOENIX-5138-v3.patch > 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.patch > > Time Spent: 1h 40m > 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)
[jira] [Updated] (PHOENIX-5138) ViewIndexId sequences created after PHOENIX-5132 shouldn't collide with ones created before it
[ https://issues.apache.org/jira/browse/PHOENIX-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Jacoby updated PHOENIX-5138: - Attachment: PHOENIX-5138-v2.patch > 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.patch > > Time Spent: 0.5h > 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)
[jira] [Updated] (PHOENIX-5138) ViewIndexId sequences created after PHOENIX-5132 shouldn't collide with ones created before it
[ https://issues.apache.org/jira/browse/PHOENIX-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Jacoby updated PHOENIX-5138: - Attachment: PHOENIX-5138.patch > 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.patch > > Time Spent: 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)
[jira] [Updated] (PHOENIX-5138) ViewIndexId sequences created after PHOENIX-5132 shouldn't collide with ones created before it
[ https://issues.apache.org/jira/browse/PHOENIX-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-5138: Fix Version/s: 5.1.0 4.15.0 > 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 > > > 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)
[jira] [Updated] (PHOENIX-5138) ViewIndexId sequences created after PHOENIX-5132 shouldn't collide with ones created before it
[ https://issues.apache.org/jira/browse/PHOENIX-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Jacoby updated PHOENIX-5138: - Affects Version/s: 5.1 Priority: Blocker (was: Major) > 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 > > 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)
[jira] [Updated] (PHOENIX-5138) ViewIndexId sequences created after PHOENIX-5132 shouldn't collide with ones created before it
[ https://issues.apache.org/jira/browse/PHOENIX-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Jacoby updated PHOENIX-5138: - Description: 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. > 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 >Reporter: Geoffrey Jacoby >Assignee: Geoffrey Jacoby >Priority: Major > > 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)
