Am 27.05.15 um 10:35 schrieb Bertrand Delacretaz: > Hi, > > On Mon, May 18, 2015 at 8:17 AM, Carsten Ziegeler <[email protected]> > wrote: >> The current resource query api has several problems: >> - it's using the JCR spec to define a query.. > > Why is that a problem? > Creating a good query API is hard work, so I'd be much more in favor > of reusing an existing query API than inventing our own. > > AFAIK Oak parses queries to the internal JCR query object model, so > translating that to a subset that random ResourceProviders can > implement should be possible.
The goal of this api is to do what I call technical queries, so queries we do in our code. Its not necessarily be used for user facing queries. Instead of using a subset of an api that doesn't look too appealing to me I would rather stay within the resource api. > >> ...Obviously this is a reduced set compared to the full fledged jcr search >> api, however it should be suitable for the majority of use cases... > > IMO it's impossible to validate such a query API in the abstract, > without having examples of how queries look, based on a set of > realistic use cases. We have queries in Sling, we have already people contributing within this thread, so I guess this works out fine. > > I'm happy to collaborate on creating these examples (which can simply > be unit tests for a relevant ResourceProvider) but before that I'd > like to discuss what the alternatives are, before we invent YAQA (*). > Make a proposal and we can discuss it Thanks Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
