[ 
https://issues.apache.org/jira/browse/OAK-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877825#comment-13877825
 ] 

Laurie byrum commented on OAK-1286:
-----------------------------------

Hi Thomas, I have no problem with the suggestions in OAK-1325 to use functions 
to expose this. That seems sensible. Regarding access rights, i don't think 
this type of query should be any different than any other query..they all 
respect ACLs, right?

> Enable/expose MoreLikeThis queries
> ----------------------------------
>
>                 Key: OAK-1286
>                 URL: https://issues.apache.org/jira/browse/OAK-1286
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: oak-lucene
>            Reporter: Laurie byrum
>            Assignee: Thomas Mueller
>             Fix For: 0.16
>
>
> The software I'm building currently makes use of Lucene's MoreLikeThis \[1\] 
> facilities in order to match user's search with Nodes in a JCR repository. 
> MoreLikeThis gives us much better results than, for example, simple full text 
> search.
> We have currently implemented this by having our own Lucene indices. For 
> simplicity and efficiency, we'd prefer to use the copy of Lucene that is 
> already built into Oak. To do so, I think we would need to add an indexer 
> config. We would also need a way to pass such queries through the jcr query 
> api. We would need something very similar to "rep:similar", but we would want 
> to be able to pass the similar text through the api (I believe the current 
> rep:similar can only take a node to be matched, as opposed to text to be 
> matched).
> \[1\] 
> http://lucene.apache.org/core/3_0_3/api/contrib-queries/org/apache/lucene/search/similar/MoreLikeThis.html



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to