[
https://issues.apache.org/jira/browse/PHOENIX-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Reid resolved PHOENIX-556.
----------------------------------
Resolution: Fixed
Bulk resolve of closed issues imported from GitHub. This status was reached by
first re-opening all closed imported issues and then resolving them in bulk.
> Surface command for disabling and rebuilding an index
> -----------------------------------------------------
>
> Key: PHOENIX-556
> URL: https://issues.apache.org/jira/browse/PHOENIX-556
> Project: Phoenix
> Issue Type: Task
> Affects Versions: 2.1.0-Release
> Reporter: James Taylor
> Assignee: James Taylor
>
> Surface support for manually disabling an index similar to the way you do it
> on SQL Server:
> ALTER INDEX my_index ON my_schema.my_table DISABLE
> A disabled index is currently continued to be maintained. Should it be?
> If we keep maintaining, then we could do this:
> ALTER INDEX my_index ON my_schema.my_table ENABLE
> Otherwise, if stop maintaining a disabled index, we can support this:
> ALTER INDEX my_index ON my_schema.my_table REBUILD
> Potentially, we could capture when the index was disabled, and only rebuild
> the data rows newer than that timestamp, or even enhance the above to:
> ALTER INDEX my_index ON my_schema.my_table REBUILD [ALL]
> We could also support something like this:
> ALTER INDEX my_index ON my_schema.my_table UNUSABLE
> ALTER INDEX my_index ON my_schema.my_table USABLE
> which would continue index maintenance, but stop the index from being used by
> queries.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
