[
https://issues.apache.org/jira/browse/PHOENIX-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor resolved PHOENIX-2984.
-----------------------------------
Resolution: Invalid
Looks like you've got this covered in updateIndexesSequenceIfPresent() call.
Nice work, [~an...@apache.org] - sorry, I missed this before.
> Ensure backward compat is not broken after PHOENIX-2901
> -------------------------------------------------------
>
> Key: PHOENIX-2984
> URL: https://issues.apache.org/jira/browse/PHOENIX-2984
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: Ankit Singhal
> Priority: Blocker
> Fix For: 4.8.0
>
>
> In PHOENIX-2901 you changed the location of the sequence for shared indexes,
> right? We'll want to make sure at upgrade time in
> ConnectionQueryServicesImpl.init() that we create the new sequence for
> existing tables with views and shared indexes and that we start the sequence
> where the old one left off. Otherwise, when you create a new shared index
> (local index or index on view), you'll repeat the sequence value since it'd
> start from 1 again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
