[
https://issues.apache.org/jira/browse/OAK-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140028#comment-15140028
]
Vikas Saurabh commented on OAK-3973:
------------------------------------
Talked to [~tmueller], and it seems that the best way to have sub-setted
suggestion would be to add it as a query language feature -- but for now, it's
alright to fix OAK-3994 with descendantnode clause. We can use this issues (and
remaining sub-tasks) to ideate around how/what to do with the new improvement.
(possibly, we can get around lucene 4.8 by that time and make something more
elegant than just sub-setting on root-paths :) )
> 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.6
>
> Attachments: OAK-3973.wip.patch
>
>
> 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)
