[ https://issues.apache.org/jira/browse/PIG-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Graham updated PIG-1946: ----------------------------- Description: Using {{HBaseStorage}} like so seems like a reasonable thing to do, but it will yield unexpected results: {code} STORE result INTO 'hbase://foo' USING org.apache.pig.backend.hadoop.hbase.HBaseStorage( 'info:first_name, info:last_name'); {code} The problem us that a column named {{info:first_name,}} will be created, with the trailing comma included. I've had numerous developers get tripped up on this issue since everywhere else in Pig variables are separated by commas, so I propose we fix it. I propose we trim leading/trailing commas from column names, but I'm open to other ideas. Also should we accept column names that are comman-delimited without spaces? was: Using {{HBaseStorage}} like so seems like a reasonable thing to do, but it will yield unexpected results: {code} STORE result INTO 'hbase://foo' USING org.apache.pig.backend.hadoop.hbase.HBaseStorage('info:first_name, info:last_name'); {code} The problem us that a column named {{info:first_name,}} will be created, with the trailing comma included. I've had numerous developers get tripped up on this issue since everywhere else in Pig variables are separated by commas, so I propose we fix it. I propose we trim leading/trailing commas from column names, but I'm open to other ideas. Also should we accept column names that are comman-delimited without spaces? > HBaseStorage constructor syntax is error prone > ---------------------------------------------- > > Key: PIG-1946 > URL: https://issues.apache.org/jira/browse/PIG-1946 > Project: Pig > Issue Type: Improvement > Reporter: Bill Graham > Assignee: Bill Graham > > Using {{HBaseStorage}} like so seems like a reasonable thing to do, but it > will yield unexpected results: > {code} > STORE result INTO 'hbase://foo' USING > org.apache.pig.backend.hadoop.hbase.HBaseStorage( > 'info:first_name, info:last_name'); > {code} > The problem us that a column named {{info:first_name,}} will be created, with > the trailing comma included. I've had numerous developers get tripped up on > this issue since everywhere else in Pig variables are separated by commas, so > I propose we fix it. > I propose we trim leading/trailing commas from column names, but I'm open to > other ideas. > Also should we accept column names that are comman-delimited without spaces? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira