[
https://issues.apache.org/jira/browse/PHOENIX-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057034#comment-14057034
]
jay wong commented on PHOENIX-1056:
-----------------------------------
[~jeffreyz]
Sometimes build all the data in a single MR is not only for performance. but
also the data consistency.
Because of the MR input path is not immutable at all.
So If we build it in multiple MR the table data may be not matched the index
data
> A ImportTsv tool for phoenix to build table data and all index data.
> --------------------------------------------------------------------
>
> Key: PHOENIX-1056
> URL: https://issues.apache.org/jira/browse/PHOENIX-1056
> Project: Phoenix
> Issue Type: Task
> Affects Versions: 3.0.0
> Reporter: jay wong
> Fix For: 3.1
>
> Attachments: PHOENIX-1056.patch
>
>
> I have just build a tool for build table data and index table data just like
> ImportTsv job.
> http://hbase.apache.org/book/ops_mgt.html#importtsv
> when ImportTsv work it write HFile in a CF name path.
> for example A table has two cf, A and B.
> the output is
> ...../outputpath/A
> ...../outputpath/B
> In my job. we has a table. TableOne. and two Index IdxOne, IdxTwo.
> the output will be
> ...../outputpath/TableOne/A
> ...../outputpath/TableOne/B
> ...../outputpath/IdxOne
> ...../outputpath/IdxTwo.
> If anyone need it .I will build a clean tool.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
