[
https://issues.apache.org/jira/browse/PHOENIX-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325702#comment-15325702
]
Ankit Singhal commented on PHOENIX-2984:
----------------------------------------
It is expected to be backward compatible as we are generating new sequences for
namespace mapped tables only and fallback to old sequence key if they are
normal tables.
But will check once again if that is not the case.
> 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)
