@Alex, Sorting wouldn't necessarily be slow. What you could do is have the API return an iterator which wraps the sorted result iterator from the various resource providers. This iterator would keep track of the next value of the iterator from every resource provider result and return the closest value for every next call of the wrapping iterator. This should result in performance of approximately On where n is the number of resource providers for each next call.
In the case where sorting isn't provided, I would think it would just interleave the results from the various resource providers. -Dan On Mon, Jun 1, 2015 at 5:00 PM, Alexander Klimetschek <aklim...@adobe.com> wrote: > On 01.06.2015, at 08:50, Carsten Ziegeler <cziege...@apache.org> wrote: > > So I think, we should support sorting across providers > > This means sorting will be very slow. Since you have to re-sort the > partial results on the sling level without usage of an index. > > Cheers, > Alex
