>From what I can tell, a fairly simple way to maintain a secondary index table in HBase is to write a co-processor that acts on the postDelete and postPut hooks of the table it is indexing for; maintaining the index as rows get deleted and inserted.
For a Put it really doesn't matter if a row is new or just updated, the indexer can simply do a Put itself; it doesn't matter if the row was already indexed, it will just get updated. But what about Delete? Is there a recommend way of detecting row deletion from the Delete object supplied to the co-processor? Or is this approach the wrong way entirely? Kind regards, Jeroen Hoek Lable
