if you know there are that few resources, then I say iterating would be better performing than XPath / JCR-SQL2 queries. This is primarily from past experience speaking in that queries have generally turned out (often MUCH) slower than directly iterating if you know what you're actually looking for.
On Thu, Jun 16, 2016 at 10:28 PM, Roy Teeuwen <r...@teeuwen.be> wrote: > Hello all, > > Lets say I got a resource with around 10-20 child/grand-child resources, > not going deeper than 3 levels max. What is the most performant when > searching for the child resources containing a specific property (the > property is configurable with OSGi, so hard to put an index on it). > Iterating the child / grand-child resources until you find it or making an > xpath/jcr-sql2 query? When would one option start to be more performant > than the other. > > Thanks! > Roy
