On Thu, Nov 6, 2014 at 2:53 PM, Chetan Mehrotra <[email protected]> wrote: > 3. AggregationIndex and IntersectionCursor - The way cursors results > are merged va intersection cursor there might be some data loss. The > intersection cursor logic would only work if the actual cursor return > result which are ordered by path. However cursor returned by > LuceneIndex are order by jcr:score. So intersection logic might miss > on some rows.
Ignore the #3 concerns as intersection cursors keep a memory of seen data from cursor so is functionally correct though it might take space if the cursor has to traverse lots and lots of rows Chetan Mehrotra
