On 24.06.2015, at 23:10, Justin Edelson <[email protected]> wrote:
> Agree, but I (and perhaps you disagree) would think this behavior would be
> totally understandable and we could make it transparent what was happening,
> i.e. have a 'show plan' output.
But note that the resource resolver level has no idea how the individual
providers implement the search and if/what of their indexes they use. Unless
you come up with a generic search index API that is exposed by the providers
(don't think that's a good idea).
> How do you see this working with the existing Sling API (i.e. before this
> addition)? Would it look like:
>
> resourceResolver.findResources("SOLR", <some solar syntax query>)
I guess you refer to "access 3rd party search index that indexes all resource
providers". In that case, not sure if you need to integrate it into the
resource resolver API, you'd talk to the 3rd party search API directly and it
should return something including resource paths that you can then lookup using
resolver.getResource().
For the other case, a query that one resource provider but not all understand,
like it is with JCR today, yes, that is what I mean.
Cheers,
Alex
