[
https://issues.apache.org/jira/browse/PHOENIX-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325452#comment-14325452
]
Lars Hofhansl commented on PHOENIX-1609:
----------------------------------------
[~giacomotaylor], it's easy enough to support HBase directly and HFiles (in
fact I added exactly that to HBase's Import command - you can either import
directly to HBase or into HFiles that are mapped afterwards).
As for the other comments. I'd vote for walking before we run, so it might be
better to start with the building blocks:
* ability to build an index asynchronously. Do we need a new syntax for it?
Something CREATE INDEX ... ASYNC? The index would be marked "disabled" or
"building", and it would be the task of the asynchronous tool to mark the index
active.
* the tools themselves. I guess one for M/R one for Spark.
* an optional tool to combine creating HFiles and loading them into HBase (the
tricky part is to do this in secure setups)
* (later) allow Phoenix to trigger this automatically.
I fear that if we try to solve everything in one go we'll never get done. If we
do the first two we have all the plumbing in place. Then we can work on making
it better/simpler.
> 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)
