You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Kadir Ozdemir (Jira)" <ji...@apache.org> on 2022/06/08 20:46:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17551790#comment-17551790 ]
Kadir Ozdemir commented on PHOENIX-6681:
----------------------------------------
[~giskender], I see the PR is closed. Can we mark this resolved? The PR was opened for 4.x. Have you merged this to the master branch too?
> 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
>
> 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.7#820007)