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

Dawid Weiss commented on SOLR-13172:
------------------------------------

MLT handler offers unique ability to match against longer content not in the 
index. This isn't fulfilled by any other implementation you mentioned. Do we 
really want to remove it without a replacement? I don't want to be a blocker 
here, but I do find this genuinely useful and like I said -- it's not the same 
as the MLT component.

> Deprecate MoreLikeTHisHandler
> -----------------------------
>
>                 Key: SOLR-13172
>                 URL: https://issues.apache.org/jira/browse/SOLR-13172
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: MoreLikeThis
>            Reporter: Alessandro Benedetti
>            Priority: Major
>
> Following the discussions with [[email protected]]
> Currently the Lucene More Like This functionality is offered in Apache Solr 
> through :
>  * More Like This Handler
>  * More Like This Component
>  * More Like This Query Parser
> The query parser is the most flexible approach and it is well supported, it 
> is a good candidate to become the main entry point if a user wnat the MLT 
> functionality.
> The More Like This component is quite coupled with the others but it has a 
> sense and offers slightly different features from the query parser ( *Using 
> MoreLikeThis as a search component returns similar documents for each 
> document in the response set.*)
> So the proposal here is to deprecate and remove the More Like This Handler, 
> to ease the maintenance  of the functionality and to simplify the way new 
> users approach it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to