[
https://issues.apache.org/jira/browse/OAK-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911464#comment-13911464
]
Thomas Mueller commented on OAK-1325:
-------------------------------------
> could be that Solr handles both native('lucene') and native('solr')
OK, that makes sense. It's not urgent however.
> cost evaluation
Sure. If "native('...')" is the only condition, then other indexes will not be
picked up, as the cost is higher. An open question is: what is the expected
behavior if there are multiple conditions, for example "where type = 'x' and
native('solr') = 'y'". I guess the query engine would use the index on "type"
in this case (if there is such an index). But I think that's good.
> 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
> Attachments: 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)
