You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2022/07/27 21:53:00 UTC

[jira] [Updated] (PHOENIX-6681) Enable new indexes to be optionally created in CREATE_DISABLED state

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

Viraj Jasani updated PHOENIX-6681:
----------------------------------
    Fix Version/s: 5.2.0

> Enable new indexes to be optionally created in CREATE_DISABLED state 
> ---------------------------------------------------------------------
>
>                 Key: PHOENIX-6681
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6681
>             Project: Phoenix
>          Issue Type: New Feature
>            Reporter: Gokcen Iskender
>            Assignee: Gokcen Iskender
>            Priority: Major
>             Fix For: 5.2.0
>
>
> When we create/drop some indexes in one datacenter, the replication pair doesn't immediately have this index and Hbase throws a replication error when we try to write into indexes that don't have a matching table on the replication pair.
> To remediate this issue, we can optionally create them in CREATE_DISABLED state and enable them after all the replication peers have the table.
> Same is true for dropping indexes. When they are dropped we can first disable them and drop them later.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)