As Shawn correctly stated, I see nothing strange in the input the More Like This. I could not think a better input to be honest for this functionality. You can potentially attach the MLT Component to your search request handler, to run the MLT on each search result, but I discourage you to do that, I think it is better to run MLT only when needed.
Can you explain us your use case, maybe as Shawn observed you don't need MLT at all. Cheers On Wed, Apr 6, 2016 at 6:07 PM, shamik <sham...@gmail.com> wrote: > Thanks Alessandro, that answers my doubt. in a nutshell, to make MLT Query > parser work, you need to know the document id. I'm just curious as why this > constraint has been added. This will not work for a bulk of use cases. For > e.g. if we are trying to generate MLT based on a text or a keyword, how > would I ever use this API ? My initial impression was that this was > designed > to work on a distributed mode. > > Now, this adds up a follow-up question as in which one is the right > approach > in a solr cloud mode. "mlt"request handler is off the equation since it's > not supported. That leaves with MoreLikeThisComponent which has a known > issue with performance. Is that the only availble solution then ? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/MLT-Query-Parser-for-SolrCloud-tp4268308p4268482.html > Sent from the Solr - User mailing list archive at Nabble.com. > -- -------------------------- Benedetti Alessandro Visiting card : http://about.me/alessandro_benedetti "Tyger, tyger burning bright In the forests of the night, What immortal hand or eye Could frame thy fearful symmetry?" William Blake - Songs of Experience -1794 England
