You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Gustavo Anatoly (JIRA)" <ji...@apache.org> on 2012/12/19 14:21:13 UTC
[jira] [Commented] (HBASE-5339) Add support for compound keys to
importtsv
[ https://issues.apache.org/jira/browse/HBASE-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535945#comment-13535945 ]
Gustavo Anatoly commented on HBASE-5339:
----------------------------------------
Hi, Lars.
I'm interested to contribute, with this improvement so I would like to know, what do you think
about to create an inner class CompoundTsvParser inside ImportTsv, and inside
CompoundTsvParser create specific parser line class?
Thanks.
> Add support for compound keys to importtsv
> ------------------------------------------
>
> Key: HBASE-5339
> URL: https://issues.apache.org/jira/browse/HBASE-5339
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
> Reporter: Lars George
> Priority: Trivial
>
> Add support that you can combine some columns from the TSV with either a given separator, no separator, or with a custom row key generator class. Syntax could be:
> {code}
> -Dimporttsv.columns=HBASE_ROW_KEY_1,HBASE_ROW_KEY_2,cf1:col1,cf2:col3,HBASE_ROW_KEY_3
> -Dimporttsv.rowkey.separator="-"
> {code}
> Another option of course is using the custom mapper class and handle this there, but this also seems like a nice to have option, probably often covering the 80% this sort of thing is needed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira