[
https://issues.apache.org/jira/browse/OAK-8271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825073#comment-16825073
]
Vikas Saurabh commented on OAK-8271:
------------------------------------
[~tmueller], no I didn't try these variations. Afaics, if some of these are
wrong then that should be fixed in query engine (oak-core).
Btw, in the meantime I realized that {{transformPath}} is used in fulltext
constraints too - so the simple diff away won't work right away. My intent is
just that the "filtering" that query engine does can (should) remain there so
that any feature/fixes are automatically incorporated.
PS: Btw, the examples I had in description work with property indexes - I
didn't check if it's due to IndexProvider or QE.
> Lucene path transformed result doesn't accomodate wildcards in relative path
> ----------------------------------------------------------------------------
>
> Key: OAK-8271
> URL: https://issues.apache.org/jira/browse/OAK-8271
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Minor
>
> {{LucenePropertyIndex}} support answering a query with property constraint on
> a relative path if there's an property (non-relative) is indexed on
> {{nt:base}}.
> e.g. with an index def such as
> {noformat}
> + /oak:index/fooIndex/indexRules/nt:base/properties
> + foo
> - propertyIndex=true
> {noformat}
> we can answer queries such as
> {noformat}
> /jcr:root/a//element(*, some:type)[b/foo='bar']
> /jcr:root/a//element(*, some:type)[b/c/foo='bar']
> {noformat}
> In the same spirit it could also support query with wildcard in relative path
> fragment
> {noformat}
> /jcr:root/a//element(*, some:type)[b/*/foo='bar']
> {noformat}
> .... but it doesn't work currently.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
