>
> Does that mean that you cannot do a 'MLT' query from one core result to get
> MLT from another (even if there is some common schema between)?
>
You can always run MLT handlers on a core. Each MLT handler takes certain
parameters based on which "similar" results are fetched. You would need to
pa
Thanks for the reply --
>> In your multi-core set-up, I don't think you are anywhere close to using
>> MLT. The arrangement looks more like a search query.
Does that mean that you cannot do a 'MLT' query from one core result
to get MLT from another (even if there is some common schema between)?
>
> My thought now is I cannot use MLT and instead must do a query to B using
> the fields from core A ID as query params. Is there big difference in what
> will be returned as results using query instead of MLT?
>
Yes, there is definitely a difference between the results from a MLT handler
and any
> Have two cores with some common fields in their schemas. I want to perform
> a MLT query on one core and get results from the other schema. Both cores
> have same type of id.
>
>Having the same "type of id" in two different cores is of no good for a MLT
>handler (which in-fact operates on one c
>
> Have two cores with some common fields in their schemas. I want to perform
> a MLT query on one core and get results from the other schema. Both cores
> have same type of id.
>
Having the same "type of id" in two different cores is of no good for a MLT
handler (which in-fact operates on one co
