[
https://issues.apache.org/jira/browse/OAK-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914369#comment-13914369
]
Thomas Mueller commented on OAK-1325:
-------------------------------------
Revision 1572503: support in oak-solr-core (based on the patch from [~teofili])
I had to change the SolrQueryIndex to be a FulltextQueryIndex, because the
query engine expects that native queries are executed by a full text index.
(This assumption that could be changed in the future).
I noticed the Solr index doesn't currently support aggregation; I added a TODO
in the constructor.
> Support native pass-through queries (e.g. Lucene)
> -------------------------------------------------
>
> Key: OAK-1325
> URL: https://issues.apache.org/jira/browse/OAK-1325
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: oak-lucene, oak-solr, query
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: 0.18
>
> Attachments: OAK-1325.1.patch, OAK-1325.patch
>
>
> The query engine currently supports XPath and SQL-2 queries as documented by
> the JCR 2.0 specification. Some queries require syntax that goes beyond the
> JCR 2.0 spec, even thought the feature is supported by the query index. One
> example is "MoreLikeThis" in OAK-1286.
> We would like an extension point so that a user of Oak can use the feature of
> the query index. There are multiple options:
> * Use a separate, custom query language (not XPath or SQL-2)
> * Extend the XPath and/or SQL-2 syntax similar to "rep:excerpt()"
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
