[
https://issues.apache.org/jira/browse/PHOENIX-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332453#comment-14332453
]
maghamravikiran commented on PHOENIX-1609:
------------------------------------------
[~jamestaylor]
Based on the comments received above, I am attaching a patch . Users can
create an index in async mode and manually trigger the MR job.
{code}
a) Create an index in async mode.
CREATE INDEX idx ON tbl (v1,v2) ASYNC
b) Trigger the job
hadoop jar phoenix-4.3.0-client.jar
org.apache.phoenix.mapreduce.index.IndexTool -dt TBL -it IDX -op /tmp/pindx
{code}
I will attach a patch for various test cases after your review.
> 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.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)
