[ https://issues.apache.org/jira/browse/OAK-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645750#comment-14645750 ]
Vikas Saurabh commented on OAK-3157: ------------------------------------ I think that we should do phrase query of {{:suggest}} field for validating access. The reason I feel so is: # We've identified a list of suggestions # The suggestions are generated from lucene-docs based of their {{:suggest}} field # We need to identify if these suggestions should be shown to end-user based on access # Phrase query on {{:suggest}} then should give us the relevant docs which contains those suggestions and hence those docs can be used to access control check. [~teofili], [~chetanm], can you guys please take a look? > Lucene suggestions don't work if suggested phrases don't return documents on > :fulltext search > --------------------------------------------------------------------------------------------- > > Key: OAK-3157 > URL: https://issues.apache.org/jira/browse/OAK-3157 > Project: Jackrabbit Oak > Issue Type: Bug > Components: lucene > Reporter: Vikas Saurabh > Attachments: LuceneIndexSuggestionTest.java > > > In current implementation, > [suggestions|http://jackrabbit.apache.org/oak/docs/query/lucene.html#Suggestions] > looks up for suggestions based on indexed properties annotated with > {{useInSuggest}}. The implementation then tries to find a document which has > this phrase (currently searched using full text search) and is readable by > the user. > In case, no such document result, then the suggestions don't show up in end > result even though the documents from which these suggestions were generated > were indeed readable by end-user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)