Issue in transactional indexing?

[Michael Segel <mi...@hotmail.com>]

All,
HBase 20.3 (yes I know we need to upgrade)...

One of the developers was trying to write a set of records to a table in hbase that has a transactional index (THBase)

In testing, they are writing records where the rowID  is based in part on a random number between 1 and n, so that over time, the row in the base table is "updated". 

We're noticing that in the index, a null value is being written to the index table which causes subsequent scans to fail.
(Since this should be the row_id in the base table, this value should never be null.)

I'm curious if there is anyone who is using the transactional indexing and have come across this issue?

Thx 

-Mike

 		 	   		  
_________________________________________________________________
Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1

RE: Issue in transactional indexing?

[Michael Segel <mi...@hotmail.com>]

Just to follow up...
Here's a message from an earlier thread that deals with the same problem...
http://osdir.com/ml/hbase-user-hadoop-apache/2010-03/msg00462.html

The reason why the scan fails with an NPE is that the index has a null in the __INDEX__ column.

So the question is if anyone has an idea why this is happening, it would be greatly appreciated.

Thx


-Mike


> From: michael_segel@hotmail.com
> To: hbase-user@hadoop.apache.org
> Subject: Issue in transactional indexing?
> Date: Fri, 25 Jun 2010 13:31:31 -0500
> 
> 
> All,
> HBase 20.3 (yes I know we need to upgrade)...
> 
> One of the developers was trying to write a set of records to a table in hbase that has a transactional index (THBase)
> 
> In testing, they are writing records where the rowID  is based in part on a random number between 1 and n, so that over time, the row in the base table is "updated". 
> 
> We're noticing that in the index, a null value is being written to the index table which causes subsequent scans to fail.
> (Since this should be the row_id in the base table, this value should never be null.)
> 
> I'm curious if there is anyone who is using the transactional indexing and have come across this issue?
> 
> Thx 
> 
> -Mike
> 
>  		 	   		  
> _________________________________________________________________
> Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox.
> http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1
 		 	   		  
_________________________________________________________________
The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. 
http://www.windowslive.com/campaign/thenewbusy?tile=multicalendar&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5