[
https://issues.apache.org/jira/browse/OAK-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912639#comment-13912639
]
Tommaso Teofili commented on OAK-1325:
--------------------------------------
Rethinking to the property / keyword for "native('$type')" what about a
property ":native('$type')" ? As far as I can see this wouldn't be a valid
property name (cannot create a node like that) and avoids changing the SQL-2
syntax so it's a bit more lightweight in that sense.
Regarding the cost evaluation I think a reasonable approach would be that if
the QueryEngine is able to satisfy that restriction then the cost is lowered
(e.g. cost /= 2).
> 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)
