[
https://issues.apache.org/jira/browse/PHOENIX-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336915#comment-14336915
]
James Taylor commented on PHOENIX-1609:
---------------------------------------
Let's tackle these issues in phase 2 and just get good unit test coverage in
place for this patch. If the index is dropped, the underlying HBase table will
be dropped, so I suspect the MR will just fail - we should have a test case for
this as well. For now, you could always pause or cancel the MR job to stop the
index build.
IMO, in phase 2, we should drive this from SQL with the MR job being kicked off
from the CREATE INDEX ASYNC command, and stop the MR job if the index is
disabled.
> MR job to populate index tables
> --------------------------------
>
> Key: PHOENIX-1609
> URL: https://issues.apache.org/jira/browse/PHOENIX-1609
> Project: Phoenix
> Issue Type: New Feature
> Reporter: maghamravikiran
> Assignee: maghamravikiran
> Attachments: 0001-PHOENIX-1609-wip.patch, 0001-PHOENIX_1609.patch
>
>
> Often, we need to create new indexes on master tables way after the data
> exists on the master tables. It would be good to have a simple MR job given
> by the phoenix code that users can call to have indexes in sync with the
> master table.
> Users can invoke the MR job using the following command
> hadoop jar org.apache.phoenix.mapreduce.Index -st MASTER_TABLE -tt
> INDEX_TABLE -columns a,b,c
> Is this ideal?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
