[
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.patch
here's a draft patch for supporting native queries for Lucene and Solr
indexers. This is based on the possibility of passing and parsing a certain
special property as a function so that a query like:
select [jcr:path] from [nt:base] where [native('solr')] = 'name:(Hello OR
World)'
would be explicitly handled by the Solr query engine in order to pass the
corresponding property value as a native query to the underlying Solr index.
This patch doesn't take (yet) into account the eventual need of retrieving
things that are not nodes from the underlying query result set (e.g. facets)
which may involve extending the current API.
> 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)
