Thanks. So I was poking through this and see that the filters are calculated up front and stored as docsets that get intersected and passed into Lucene in the filter. The question though is that somewhere in the IndexSearcher and somewhere into the scorer it does this but I can't quite find where.
Thanks Amit On Sat, Oct 20, 2012 at 5:22 PM, Mikhail Khludnev <mkhlud...@griddynamics.com> wrote: > Amit, > > Sure. this method > https://github.com/apache/lucene-solr/blob/trunk/solr/core/src/java/org/apache/solr/search/SolrIndexSearcher.java#L796beside > some other stuff calculates fq's docset intersection which is > supplied into filtered search call > https://github.com/apache/lucene-solr/blob/trunk/solr/core/src/java/org/apache/solr/search/SolrIndexSearcher.java#L1474 > > You are welcome. > > On Sun, Oct 21, 2012 at 12:00 AM, Amit Nithian <anith...@gmail.com> wrote: > >> Hi all, >> >> Quick question. I've been reading up on the filter query and how it's >> implemented and the multiple articles I see keep referring to this >> notion of leap frogging and filter query execution in parallel with >> the main query. Question: Can someone point me to the code that does >> this so I can better understand? >> >> Thanks! >> Amit >> > > > > -- > Sincerely yours > Mikhail Khludnev > Tech Lead > Grid Dynamics > > <http://www.griddynamics.com> > <mkhlud...@griddynamics.com>