jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Mueller <muel...@adobe.com>
Subject Re: Re (OAK-36) Implement a query parser - what about indexing?
Date Mon, 26 Mar 2012 11:59:50 GMT

>Currently, for Hippo, I am doing something
>similar for the query api, that can seamlessly delegate to Solr or
>jackrabbit, both returning a jcr node iterator (although the solr
>index through solrj can also return plain pojo's). I really like the
>first option (pre-commit example) and third (observation based), and
>still see many bears on the road for the second (full-text on

Would it make sense to implement this in Oak? Or do you prefer an external

>I've one more question regarding the oak search/indexes : Will we be
>able to query that returns something else than jcr nodes/rows? I
>frequently want to be able to get a query result from the repository
>that cannot be returned as node iterators. For example query on stats,
>or a query for 'auto-completion' on some property (thus return some
>part of the TermEnum for example)

Could you give a few concrete examples? What would such a query look like,
and what kind of data would it return?


View raw message