m 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
, 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 wrote:
> Thanks Alessandro, that answers my doubt. in a nutshell, to make MLT Query
> parser work,
On 4/6/2016 11:07 AM, shamik 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
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
ot;name" ".
According to what you wrote : "
Right now,I'm getting mlt documents based on a "keyword"
field"
I think the query you want is simply :
{!mlt qf=keyword}
For MLT query parser the document id is the only input supported.
Cheers
On Wed, Apr 6, 2016
Hi,
I'm trying to use the new MLT query parser in a SolrCloud mode. As per
the documentation, here's the syntax,
{!mlt qf=name}1
where "1" is the id.
What I'm trying to undertsand is whether "id" is a mandatory field in
making this work? Right now,I
