IndexedTable will always be much slower than HTable.
HTable is just the client interface to HBase. IndexedTable is a special
facility that extends HTable to allow for secondary-index queries in a
single query.
The reason it's much slower is because it's actually two separate
queries. First you go to the index table, then you go to the indexed
table. Two queries, I'd expect 1.5-2X slower.
JG
Ramesh.Ramasamy wrote:
Hi St.Ack,
In 0.19.x, this facility is experimental but works.
Does it meant, It may/ not give faster data read, than HTable?
In my case, still HTable is giving better performance than IndexedTable (I'm
experimenting this with HBase 0.19.1. my sample IndexedTable has 1 Family
with 12 qualifiers, 35 millions of rows..may be I should try this as a Wide
table, instead of Tall table which I have presently)
The combination of HTable + ColumnValueFilter is awesome, but not
IndexedTable + ColumnValueFilter.
TIA,
Ramesh
