[
https://issues.apache.org/jira/browse/PHOENIX-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14296071#comment-14296071
]
Dave Hacker commented on PHOENIX-1609:
--------------------------------------
We also need to make sure to handle the time stamps properly when populating
the index table. I believe current index population sets timestamp of the rows
for the initial population to the time index creation starts. It will need to
be the same across all rows.
Another thing we probably should start considering with the map reduce
integration is how does a Phoenix client monitor the status of it. Is there
already an existing way to do this or should we file a separate jira for this?
> 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
>
> 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)
