jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Parvulescu <alex.parvule...@gmail.com>
Subject Asynchronous indexing consistency
Date Wed, 29 May 2013 09:06:06 GMT
hi guys,

I'm trying to find a solution for keeping the async index up to date in the
case where the system restarts.
How can the indexing process pick up where it left off?

A quick chat with Jukka turned up some ideas, but be warned this is all
based on api changes:

 - expose the revision info and make it usable from the NodeStore.
The indexer would need to access the rev info, eventually store it, use it
as a reference when creating a new index branch.

 - have a persistent (not garbage collected) branch dedicated to the async
indexer, which it can reuse even after a restart, eventually dispose of it
when the indexing process is done with.
This is an optimization of the entire index branch creation bits.

So, missing apis:
 - revision info in the NodeState,
 - possibility to get the NodeState given a revision, (so that we can have
the diff from rev to head)
 - branch creation with a name, branch retrieval by name, branch delete by


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message