[
https://issues.apache.org/jira/browse/PHOENIX-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gokcen Iskender updated PHOENIX-6681:
-------------------------------------
Description:
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.
was:
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 optionally have
them in DROP_DISABLED state and actually drop them later.
> Enable new indexes to be optionally created in CREATE_DISABLED state and also
> optionally drop them with DROP_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.1#820001)
