What is the empty column value in the index table (actual hbase table) for corresponding row?
Did you use IndexTool to rebuild the index?
Hey Josh! I'm glad you show up!
>> Did you `select * from index_table` verbatim?
Yes. Because I found that as long as the query goes to index (checked from EXPLAIN), the result must be empty. So I checked what're inside index by select * index.
>> Caveat about covered columns in a query
Data table is (A primary key, B, C, D, E, ...), index on B include C . B, C columns are nullable.
>> What's the state of the index?
Index_state shows "a". What does it mean?
>> * Did you use Phoenix to create the data+index tables and to populate the data in those tables?
From: Josh Elser <email@example.com>
Sent: 30 March 2020 23:42
Subject: Re: Select * gets 0 rows from index table
Can you clarify a couple of things?
* What version of Phoenix?
* Did you `select * from index_table` verbatim? Most of the time, when
you have an index table, you'd be interacting with the data table which
(behind the scenes) goes to the index table.
* * Caveat about covered columns in a query
* What's the state of the index? Look at the INDEX_STATE column in
system.catalog for your index table.
* Did you use Phoenix to create the data+index tables and to populate
the data in those tables?
On 3/30/20 4:35 AM, Reid Chan wrote:
> Hi team,
> I encountered a problem that select * from index_table limit x got 0 rows, but underlying hbase has data (observed it from hbase shell > scan) and any queries went to index table would get 0 rows as well.
> In the meantime the server had the following error message: "index.GlobalIndexChecker: Could not find the newly rebuilt index row with row key xxx for table yyy."
> Looking forward to get some hints from experienced users and devs.
> Best regards,