By the way, the queries end up in the filterCache regardless of the value set in useFilterForSortedQuery.
Thanks, Markus -----Original message----- > From:Markus Jelsma <markus.jel...@openindex.io> > Sent: Thursday 3rd May 2018 12:05 > To: solr-user@lucene.apache.org; solr-user <solr-user@lucene.apache.org> > Subject: RE: User queries end up in filterCache if facetting is enabled > > Thanks Mikhail, > > But i thought about that setting too, but i do sort by score, as does Solr > /select handler by default. The enum method accounts for all the values for a > facet field, but not the user queries i see ending up in the cache. > > Any other suggestions to shed light on this oddity? > > Thanks! > Markus > > > > -----Original message----- > > From:Mikhail Khludnev <m...@apache.org> > > Sent: Thursday 3rd May 2018 9:43 > > To: solr-user <solr-user@lucene.apache.org> > > Subject: Re: User queries end up in filterCache if facetting is enabled > > > > I mean > > https://lucene.apache.org/solr/guide/6_6/query-settings-in-solrconfig.html#QuerySettingsinSolrConfig-useFilterForSortedQuery > > > > > > On Thu, May 3, 2018 at 10:42 AM, Mikhail Khludnev <m...@apache.org> wrote: > > > > > Enum facets, facet refinements and https://lucene.apache.org/ > > > solr/guide/6_6/query-settings-in-solrconfig.html comes to my mind. > > > > > > On Wed, May 2, 2018 at 11:58 PM, Markus Jelsma <markus.jel...@openindex.io > > > > wrote: > > > > > >> Hello, > > >> > > >> Anyone here to reproduce this oddity? It shows up in all our collections > > >> once we enable the stats page to show filterCache entries. > > >> > > >> Is this normal? Am i completely missing something? > > >> > > >> Thanks, > > >> Markus > > >> > > >> > > >> > > >> -----Original message----- > > >> > From:Markus Jelsma <markus.jel...@openindex.io> > > >> > Sent: Tuesday 1st May 2018 17:32 > > >> > To: Solr-user <solr-user@lucene.apache.org> > > >> > Subject: User queries end up in filterCache if facetting is enabled > > >> > > > >> > Hello, > > >> > > > >> > We noticed the number of entries of the filterCache to be higher than > > >> we expected, using showItems="1024" something unexpected was listed as > > >> entries of the filterCache, the complete Query.toString() of our user > > >> queries, massive entries, a lot of them. > > >> > > > >> > We also spotted all entries of fields we facet on, even though we don't > > >> use them as filtes, but that is caused by facet.field=enum, and should be > > >> expected, right? > > >> > > > >> > Now, the user query entries are not expected. In the simplest set up, > > >> searching for something and only enabling the facet engine with > > >> facet=true > > >> causes it to appears in the cache as an entry. The following queries: > > >> > > > >> > http://localhost:8983/solr/search/select?q=content_nl:nog&facet=true > > >> > http://localhost:8983/solr/search/select?q=*:*&facet=true > > >> > > > >> > become listed as: > > >> > > > >> > CACHE.searcher.filterCache.item_*:*: > > >> > org.apache.solr.search.BitDocSet@​70051ee0 > > >> > > > >> > CACHE.searcher.filterCache.item_content_nl:nog: > > >> > org.apache.solr.search.BitDocSet@​13150cf6 > > >> > > > >> > This is on 7.3, but 7.2.1 does this as well. > > >> > > > >> > So, should i expect this? Can i disable this? Bug? > > >> > > > >> > > > >> > Thanks, > > >> > Markus > > >> > > > >> > > > >> > > > >> > > > >> > > > > > > > > > > > > -- > > > Sincerely yours > > > Mikhail Khludnev > > > > > > > > > > > -- > > Sincerely yours > > Mikhail Khludnev > > >
