[
https://issues.apache.org/jira/browse/OAK-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130750#comment-15130750
]
Vikas Saurabh commented on OAK-3973:
------------------------------------
While trying a few things, the simplest way to hack into ACL check mechanism
was to add path constraint while querying for {{SUGGEST}} field (or
correspondingly for spell check too). To add the path constraint, we have at
least 2 options:
* Utilize {{:ancestors}} field - but that's available only if
evaluatePathRestriction is et
* Add range constraint on {{:path}} as {{:path:[<rootPath>/ TO <rootPath>0]}}
(the same idea that we utilize while querying children docs from mongo)
[~chetanm], [~teofili], thoughts?
> 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)
