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 at collection1 just won't hit
filter cache, and will be cached as new entry and lately the old entry will
be evicted.
On Tue, Jan 15, 2019 at 5:30 PM Vadim Ivanov <
vadim.iva...@spb.ntk-intourist.ru> wrote:
> 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 fromIndex=collection2 to=field1}*:*
>
> > 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 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 to use caches on
> > > collection1 and ...
> > > Does new searcher starts on collection1 as well?
> > >
> > >
> > > > -----Original Message-----
> > > > From: Vadim Ivanov [mailto:vadim.iva...@spb.ntk-intourist.ru]
> > > > Sent: Tuesday, January 15, 2019 1:00 PM
> > > > To: solr-user@lucene.apache.org
> > > > Subject: join query and new searcher on joined collection
> > > >
> > > > Solr 6.3
> > > >
> > > >
> > > >
> > > > I have a query like this:
> > > >
> > > > q=*:*{!join score=none from=id fromIndex=hss_4 to=rpk_hdquotes
> > v=$qq}*:*
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Vadim
> > > >
> > > >
> > >
> > >
> > >
> >
> > --
> > Sincerely yours
> > Mikhail Khludnev
>
>
--
Sincerely yours
Mikhail Khludnev
