On Mon, Jun 20, 2016 at 4:47 PM, Jason E Bailey <jason.bai...@24601.org> wrote: > ...Maybe I should file a bug report. "Hey why is it that I can iterate and > get results faster than doing an indexed query?"...
That's not a bug, that's a feature ;-) JCR naturally enables very efficient navigation between nodes that are close to each other (in terms of tree hops) so if you're working in a fairly compact subtree JCR navigation is often much more efficient than querying. The trick is to design your tree structures with this in mind - things that usually go together should stay close to each other in the JCR content tree, whenever possible. As David's model [1] says, "drive the content hierarchy, don't let it happen". -Bertrand [1] https://wiki.apache.org/jackrabbit/DavidsModel
