[
https://issues.apache.org/jira/browse/PHOENIX-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334551#comment-14334551
]
maghamravikiran edited comment on PHOENIX-1609 at 2/24/15 7:43 AM:
-------------------------------------------------------------------
Thanks [~jamestaylor] for the feedback. Would it be ok if we call disableTable
on the underlying HBase table . That way, the MR job will fail to copy HFiles
as the index table is disabled.
was (Author: [email protected]):
Thanks [~jamestaylor] for the feedback. Would it be ok if we call disableTable
on the underlying HBase table . That way, the MR job will fail to copy HFiles
as the index table is marked DISABLE.
> 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)
