Have you tried this with Cache=false? https://wiki.apache.org/solr/CommonQueryParameters#Caching_of_filters
Because the internal representation of the field value already may be doing what you want. And the caching of non-repeating filters is what slowing it down. I would just do that as a sanity check (no need to reindex, just a query string change) before going deeper into custom components. Regards, Alex. ---- Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter: http://www.solr-start.com/ On 18 August 2015 at 09:57, Norgorn <lsunnyd...@mail.ru> wrote: > I'm sorry for being so unclear. > The problem is in speed - while node holds only several cats, it can answer > with "numFound=0", if these cats are missed in query. > > It looks like: > node 1 - cats 1,2,3 > node 2 - cats 3,4,5 > node 3 - cats 50,70 > ... > > Query "q=cat:(1 4)" > > QTime per node now is like > node1 - 1300 > node2 - 1200 > node3 - 1500 (sometimes) > ... > > But I want to achieve > node1 - 1300 > node2 - 1200 > node3 - 100 > > I know that /filterCache/ helps, but I don't want values for "cat" filter to > be evicted at all. > > So I'm looking for a solution to keep separate cache, or something else. > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-cache-for-specific-field-tp4223651p4223660.html > Sent from the Solr - User mailing list archive at Nabble.com.
