Hi Davide, Interesting, this was not even merged to 1.0 yet and it's already being used for other-than-mentioned purposes :)
Drawbacks are around the fact that the async indexes are stale (falling behind) so they will report old data to any query that hits them. Other than than, issues could pop up around the volume of data being indexed, but that is index implementation specific. hope this helps, alex On Mon, Aug 4, 2014 at 1:56 PM, Davide Giannella <[email protected]> wrote: > On 04/08/2014 11:49, Alex Parvulescu wrote: > > 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. > > > Awesome! > > Side thinking. I know we stated to be used for debug but I see clients > doing it for big bunch of imports. Let's say 5M nodes. > > Do we foresee any drawbacks with diffing a state of somewhere around 5M > nodes behind? Other than the actual indexing itself I mean. > > D. > > >
