hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From anil gupta <anilg...@buffalo.edu>
Subject Re: Bulk loading a CSV file into HBase
Date Thu, 08 Mar 2012 19:14:43 GMT
Hi Stack,

Yes, the separator argument is sensitive to position in the command.
Currently, it needs to be specified just after program name. The same is
not mentioned in the docs.

I have got two suggestion for fixing this so that other don't run into same

1. Update the HBase bulk load documentation and specify that separator
argument should be next to program name.
2. Fix the problem in the code itself by handling the separator argument
explicitly. (Still, i am wondering why only separator value is not being
set in jobconf automatically if it is not provided next to program name??)

What's your take?


On Thu, Mar 8, 2012 at 9:12 AM, Stack <stack@duboce.net> wrote:

> On Wed, Mar 7, 2012 at 11:59 PM, anil gupta <anilgupt@buffalo.edu> wrote:
> > I tried to analyze the problem and as per my analysis there is a problem
> > with "String[] otherArgs = new GenericOptionsParser(conf,
> > args).getRemainingArgs();" on line#102. Let me know you views.
> >
> So, its just where you put the option on the command line?  If its on
> the end, my guess is its presumed the arg is for the program.  If its
> before the program name, then its for GenericOptionsParser to digest.
> Thats sort of how it is expected to work I'd say.  Its confusing
> though?  Can we do anything in the usage for the importtsv tool to
> make it so others don't have this issue?
> Thanks,
> St.Ack

Thanks & Regards,
Anil Gupta

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message