You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/06/10 18:42:20 UTC

[jira] [Updated] (PHOENIX-2984) Ensure backward compat is not broken after PHOENIX-2901

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

James Taylor updated PHOENIX-2984:
----------------------------------
    Fix Version/s: 4.8.0

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