[
https://issues.apache.org/jira/browse/PHOENIX-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056538#comment-14056538
]
Jeffrey Zhong commented on PHOENIX-1056:
----------------------------------------
Other issues can be easily addressed except the index hfile region boundary
alignment during MR otherwise LoadIncrementalHFiles will become a heavy
operation.
[~jaywong] Have you tried ImportTsv tool internally so that you might be able
to see what's the performance difference between one single MR(plus loading
hfiles) and multiple MR concurrently?
> 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)
