[
https://issues.apache.org/jira/browse/OAK-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13873352#comment-13873352
]
Tommaso Teofili commented on OAK-1325:
--------------------------------------
Can SQL-2 functions like the one provided by DBMSs (e.g. MySQL ones here:
http://dev.mysql.com/doc/refman/5.0/en/functions.html) be an option?
We could then let each query engine implementation expose its own specific
functions and, if I get it right, still keep it fully JCR 2.0 compatible.
In the MLT (OAK-1286) scenario it may be something like: select * from
[nt:unstructured] where MLT("bla bla native indexer mlt query")
One other thing that I had in mind is how to eventually expose other than the
usual information in the results if a query engine is able / wants to do that
(e.g. facets for Lucene and Solr engines), probably worth another issue but
still related to this as it may lead to changing APIs.
> 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
>
> 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)
