St.Ack,
Thanks a lot for the comment! In my case, keeping it all together is
more important, so I stay with the IndexedTable.
--Kirill
stack wrote:
On Mon, Nov 23, 2009 at 1:10 AM, Kirill Shabunov <[email protected]> wrote:
Hi!
In the previous thread it is mentioned it is not recommended to use
built-in secondary indexes (IndexedTable) and one should build its own
secondary index instead. Could anyone comment on this?
IndexedTable is a subclass of Transactional HBase. It uses transactions to
ensure that both the primary and secondary inserts happen (rolling back if
one of the inserts fails). I don't think Amandeep is saying do not use
IndexedTable. He is just suggesting that you might want to maintain your
own secondary indices rather than go via IndexedTable. Because IndexedTable
uses transactions, the writes can be bit slower. Maybe write speed is
important for your application? But using IndexedTable, you can be sure the
secondary table insert has happened. Maybe this latter aspect is of more
import?
St.Ack
