[
https://issues.apache.org/jira/browse/PIG-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033148#comment-13033148
]
Bill Graham commented on PIG-1946:
----------------------------------
The column descriptors take anything I can throw at them:
{code}
hbase(main):001:0> create 't1', {NAME => 'f1', VERSIONS => 5}
0 row(s) in 0.6400 seconds
hbase(main):002:0> put 't1', 'r1', 'f1:!@#$%)(:+_-=\][{}|;:"><,./?`~', 'value'
0 row(s) in 0.0660 seconds
{code}
I'm also able to create column families with both '/' and '\' in them. Any
suggestions for a valid encoding scheme?
> 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
> Fix For: 0.10
>
> Attachments: PIG-1946_1.patch
>
>
> 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
