hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manaswini (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13788) Shell commands do not support column qualifiers containing colon (:)
Date Fri, 03 Feb 2017 17:01:52 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15851734#comment-15851734
] 

Manaswini commented on HBASE-13788:
-----------------------------------

Thanks for the review @Stack. 

Yes, you are right "x:twitter:username" is not there in my dataset especially if I use put
to get the data in.

With existing code
hbase(main):009:0> create 'content3', {NAME => 'x', BLOOMFILTER => 'NONE', REPLICATION_SCOPE
=> '0', VERSIONS => '3', COMPRESSION => 'NONE', MIN_VERSIONS => '0', TTL =>
'2147483647', BLOCKSIZE => '65536', IN_MEMORY => 'false', BLOCKCACHE => 'true'}
0 row(s) in 1.4300 seconds

=> Hbase::Table - content3
hbase(main):010:0> put 'content3','A:9223370612089311807:twtr:570133798827921409','x:twitter:username',
'BERITA & INFORMASI!'
0 row(s) in 0.1350 seconds

hbase(main):011:0> scan 'content3'
ROW                               COLUMN+CELL                                            
                                        
 A:9223370612089311807:twtr:57013 column=x:twitter, timestamp=1486141128707, value=BERITA
& INFORMASI!                            
 3798827921409                                                                           
                                        
1 row(s) in 0.0150 seconds
  
 Ordinal is a great idea but what if the user has a hundred columns in COLUMNS and only wants
to format a few. I think having both the options will be useful. I'll need to dig further
into the code to see if that's doable with minimal changes/impacts


> Shell commands do not support column qualifiers containing colon (:)
> --------------------------------------------------------------------
>
>                 Key: HBASE-13788
>                 URL: https://issues.apache.org/jira/browse/HBASE-13788
>             Project: HBase
>          Issue Type: Bug
>          Components: shell
>    Affects Versions: 0.98.0, 0.96.0, 1.0.0, 1.1.0
>            Reporter: Dave Latham
>            Assignee: Manaswini
>
> The shell interprets the colon within the qualifier as a delimiter to a FORMATTER instead
of part of the qualifier itself.
> Example from the mailing list:
> Hmph, I may have spoken too soon. I know I tested this at one point and
> it worked, but now I'm getting different results:
> On the new cluster, I created a duplicate test table:
> hbase(main):043:0> create 'content3', {NAME => 'x', BLOOMFILTER =>
> 'NONE', REPLICATION_SCOPE => '0', VERSIONS => '3', COMPRESSION =>
> 'NONE', MIN_VERSIONS => '0', TTL => '2147483647', BLOCKSIZE => '65536',
> IN_MEMORY => 'false', BLOCKCACHE => 'true'}
> Then I pull some data from the imported table:
> hbase(main):045:0> scan 'content', {LIMIT=>1,
> STARTROW=>'A:9223370612089311807:twtr:57013379'}
> ROW                                  COLUMN+CELL
> ....
> A:9223370612089311807:twtr:570133798827921408
> column=x:twitter:username, timestamp=1424775595345, value=BERITA &
> INFORMASI!
> Then put it:
> hbase(main):046:0> put
> 'content3','A:9223370612089311807:twtr:570133798827921408',
> 'x:twitter:username', 'BERITA & INFORMASI!'
> But then when I query it, I see that I've lost the column qualifier
> ":username":
> hbase(main):046:0> scan 'content3'
> ROW                                  COLUMN+CELL
>  A:9223370612089311807:twtr:570133798827921408 column=x:twitter,
>  timestamp=1432745301788, value=BERITA & INFORMASI!
> Even though I'm missing one of the qualifiers, I can at least filter on
> columns in this sample table.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message