[
https://issues.apache.org/jira/browse/OAK-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili updated OAK-1325:
---------------------------------
Attachment: OAK-1325.1.patch
second patch supporting a "native()" function in SQL2 which, after a further
thought, looks a bit better. So the query for native Lucene query would look
like:
select [jcr:path] from [nt:base] where native('lucene') = 'title:foo -title:bar'
then the native('lucene') function gets transformed into a property restriction
on the virtual property "native('lucene')" which has to be explicitly handled
by the specific QueryEngine implementations.
I've adapted the cost calculation a bit to reduce the calculated cost if the
query engine is able to parse that query (however that doesn't seem to me good
enough for the final version of the cost calculation, but that deserves a
separate issue in my opinion)
> 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.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)
