I’m talking about the filterCache. You said you were using this in a “filter query”, which I assume is an “fq” clause, which is automatically cached in the filterCache.
It would help a lot if you told us two things: 1> what the clause looks like. You say 1,500 strings. How are you assmebling them? 2> what the field definition is… Best, Erick > On May 31, 2019, at 12:53 AM, Venkateswarlu Bommineni <bvr...@gmail.com> > wrote: > > Tim/Eric, > > @Tim : We do have category field in existing solr configuration. So the > existing functionality is we will query based on category and get the > results from solr and display them on PCAT. > > But as per new requirement , we need to invoke third party service to fetch > the personalized products and send them to Solr get the results. that is > the reason i was tying to send those products in solr query. > > @Eric : we are using Solr 7.2.1 version. I will check on solr cache. > > Thanks, > Venkat. > > On Thu, May 30, 2019 at 7:53 PM Erick Erickson <erickerick...@gmail.com> > wrote: > >> What version of Solr? Recent versions automatically use terms query parser >> for large, simple or clauses. Do look into using it anyway. And I'd set >> cache=false because I doubt you'll ever get a cache hit... >> >> On Thu, May 30, 2019, 16:21 Venkateswarlu Bommineni <bvr...@gmail.com> >> wrote: >> >>> Hello Team, >>> >>> I have got a requirement to send many strings (~1500) in the filter query >>> param to the solr. >>> >>> Can you please provide any suggestions/precautions we need to take care >> in >>> this particular scenario. >>> >>> Thanks, >>> Venkat. >>> >>
