Thanks Shawn and Alessandro. I get the part why id is needed. I was trying to compare with the "mlt" request handler which doesn't enforce such constraint. My previous example of title/keyword is not the right one, but I do have fields which are unique to each document and can be used as a key to extract similar content. I don't think we can always have handle to the document id in every scenario. In my case, it's a composite id and I don't pass it back and forth as part of search results. For e.g. when I'm trying to get similar content for a specific forum thread, I could very well use the threadId field stored in Solr (unique to each document) to generate similar content. This works great using "mlt" request handler. I was expecting the query parser will have similar capability.
-- View this message in context: http://lucene.472066.n3.nabble.com/MLT-Query-Parser-for-SolrCloud-tp4268308p4268759.html Sent from the Solr - User mailing list archive at Nabble.com.
