You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by y_...@tsmc.com on 2010/01/07 07:24:25 UTC

problem of secondary index


I've created a table named table1 with a secondary index idx1.
Trying to put millons of rows data; most index were built well,
which means I can get the data by index.
Unfortunately, There is a weird combination like following:
I can find a row in index table but fail in the main table;
that means there's some problem in index transaction?
Any ideas?

hbase(main):008:0> get 'table1-idx1','indexValueKeyValue'
COLUMN                       CELL
 MAJOR:idx1                  timestamp=1262799230147, value=indexValue
 __INDEX__:ROW               timestamp=1262799230147, value=KeyValue
2 row(s) in 0.3150 seconds

--------------------------------------------------------------------------------------------------------
hbase(main):009:0> get 'table1','KeyValue'
10/01/07 13:49:53 DEBUG client.HConnectionManager$TableServers: Cache hit
for row <> in tableName FRPD: location server 10.42.253.212:60020, location
region name FRPD,,1262786155692
0 row(s) in 0.2100 seconds



Fleming Chiu(邱宏明)
707-6128
y_823910@tsmc.com
週一無肉日吃素救地球(Meat Free Monday Taiwan)


 --------------------------------------------------------------------------- 
                                                         TSMC PROPERTY       
 This email communication (and any attachments) is proprietary information   
 for the sole use of its                                                     
 intended recipient. Any unauthorized review, use or distribution by anyone  
 other than the intended                                                     
 recipient is strictly prohibited.  If you are not the intended recipient,   
 please notify the sender by                                                 
 replying to this email, and then delete this email and any copies of it     
 immediately. Thank you.                                                     
 --------------------------------------------------------------------------- 




Re: problem of secondary index

Posted by Jean-Daniel Cryans <jd...@apache.org>.
I'm not an expert on the indexed contrib but by looking a bit a the
code, it just looks like that's how the secondary index table is
built. Since the shell doesn't "talk" the same language as the
contrib, it shows you the raw data.

J-D

2010/1/6  <y_...@tsmc.com>:
>
>
> I've created a table named table1 with a secondary index idx1.
> Trying to put millons of rows data; most index were built well,
> which means I can get the data by index.
> Unfortunately, There is a weird combination like following:
> I can find a row in index table but fail in the main table;
> that means there's some problem in index transaction?
> Any ideas?
>
> hbase(main):008:0> get 'table1-idx1','indexValueKeyValue'
> COLUMN                       CELL
>  MAJOR:idx1                  timestamp=1262799230147, value=indexValue
>  __INDEX__:ROW               timestamp=1262799230147, value=KeyValue
> 2 row(s) in 0.3150 seconds
>
> --------------------------------------------------------------------------------------------------------
> hbase(main):009:0> get 'table1','KeyValue'
> 10/01/07 13:49:53 DEBUG client.HConnectionManager$TableServers: Cache hit
> for row <> in tableName FRPD: location server 10.42.253.212:60020, location
> region name FRPD,,1262786155692
> 0 row(s) in 0.2100 seconds
>
>
>
> Fleming Chiu(邱宏明)
> 707-6128
> y_823910@tsmc.com
> 週一無肉日吃素救地球(Meat Free Monday Taiwan)
>
>
>  ---------------------------------------------------------------------------
>                                                         TSMC PROPERTY
>  This email communication (and any attachments) is proprietary information
>  for the sole use of its
>  intended recipient. Any unauthorized review, use or distribution by anyone
>  other than the intended
>  recipient is strictly prohibited.  If you are not the intended recipient,
>  please notify the sender by
>  replying to this email, and then delete this email and any copies of it
>  immediately. Thank you.
>  ---------------------------------------------------------------------------
>
>
>
>