[
https://issues.apache.org/jira/browse/OAK-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130743#comment-15130743
]
Vikas Saurabh commented on OAK-3973:
------------------------------------
Another possible idea is to have property restriction on {{jcr:path}}. While
this being more counter-intuitive, the has a couple of advantages:
* implementation wise it touches less code - only one class in oak-lucene
* it can allow for looking into a set of paths by saying {{[jcr:path]="/a" OR
[jcr:path]="/b"}}
[~tmueller], it'd great to have your insight here.
> There should be a way to get filtered suggestions based on some path
> --------------------------------------------------------------------
>
> Key: OAK-3973
> URL: https://issues.apache.org/jira/browse/OAK-3973
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Fix For: 1.4
>
>
> Currently, suggestions are indexed at index level - so, when querying for
> suggestions, the result incorporates all documents indexed by that document.
> So, this doesn't allow filtering suggestions for a subset of indexed document
> - at least we should be able to get filtered suggestion based on a root path.
> This seems very similar to a functionality provided by lucene vide
> LUCENE-5528 which was fixed in lucene 4.8. Since oak is still on 4.7, so, we
> can't exploit that feature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
