You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "maghamravikiran (JIRA)" <ji...@apache.org> on 2015/03/02 04:34:04 UTC

[jira] [Updated] (PHOENIX-1609) MR job to populate index tables

     [ https://issues.apache.org/jira/browse/PHOENIX-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

maghamravikiran updated PHOENIX-1609:
-------------------------------------
    Attachment: 0001-PHOENIX-1609-4.0.patch

[~jamestaylor] 
    I have attached a latest patch with few test cases. Please 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-4.0.patch, 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)