I see, thank you very much!
> -Original Message-
> From: Mikhail Khludnev [mailto:m...@apache.org]
> Sent: Tuesday, January 15, 2019 6:45 PM
> To: solr-user
> Subject: Re: join query and new searcher on joined collection
>
> It doesn't invalidate anything. It j
It doesn't invalidate anything. It just doesn't matches to the join query
from older collection2 see
https://github.com/apache/lucene-solr/blob/b7f99fe55a6fb6e7b38828676750b3512d6899a1/solr/core/src/java/org/apache/solr/search/JoinQParserPlugin.java#L570
So, after commit collection2 following join
Thanx, Mikhail for reply
> collection1 has no idea about new searcher in collection2.
I suspected it. :)
So, when "join" query arrives searcher on collection1 has no chance to use
filter cache, stored before.
I suppose it invalidates filter cache, am I right?
&fq={!join score=none from=id fromI
collection1 has no idea about new searcher in collection2.
On Tue, Jan 15, 2019 at 1:18 PM Vadim Ivanov <
vadim.iva...@spb.ntk-intourist.ru> wrote:
> Sory, I've sent unfinished message
> So, query on collection1
> q=*:*{!join score=none from=id fromIndex=collection2 to=field1}*:*
>
> The question
Sory, I've sent unfinished message
So, query on collection1
q=*:*{!join score=none from=id fromIndex=collection2 to=field1}*:*
The question is what happened with autowarming and new searchers on
collection1 when new searcher starts on collection2?
IMHO when request with join comes it's impossible
