[
https://issues.apache.org/jira/browse/PHOENIX-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14324604#comment-14324604
]
James Taylor commented on PHOENIX-1609:
---------------------------------------
If a user has to execute a separate MR job from the client, then that client
has to be configured correctly as well. Seems like it just shifts the config
requirements there and adds an extra step. I think any new dependencies can be
baked into the phoenix client jar. What's involved in making sure that a
Phoenix client is configured to be able to run a MR job? Also, FWIW, if the MR
job fails, we can fall back to our current index building mechanism.
> 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)
