Hi Davide, The way the async indexer works is it keeps a reference to the last indexed revision, and on the next run it will build a diff containing everything since. So when you resume it will include everything that changed already without needed a full reindex.
best, alex On Mon, Aug 4, 2014 at 11:39 AM, Davide Giannella <[email protected]> wrote: > On 31/07/2014 15:47, [email protected] wrote: > > Author: alexparvulescu > > Date: Thu Jul 31 13:47:06 2014 > > New Revision: 1614891 > > > > URL: http://svn.apache.org/r1614891 > > Log: > > OAK-2004 Add a way to pause the background async indexer > > > Didn't look deeply into the commit. Did we consider the fact that when > the index is resumed it should spool any commit that came while paused? > If not, should we run then a reindex with the consequent time taken for > re-indexing large repositories? > > D. > > >
