One more thought: If caching is not feasible for any reason, it would be also good do implements hints to force usage of specified index (OAK-937). It will allow to skip cost calculation altogether for queries by using hints. Advanced developer and/or some internal queries could leverage from this.
On Fri, Aug 14, 2015 at 4:36 PM, pacoolsky . <[email protected]> wrote: > I looked there some time ago, and raised the related ticket > https://issues.apache.org/jira/browse/OAK-2777. I didn't continue further > on this because I've seen caching is on the roadmap. > > I think the ReferenceIndex is a good candidate to start with. It > definitely can help with Repository.login queries. > > Regards, Przemo Pakulski >
