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
th
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
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
wrote:
> Hello Team,
>
> I have got a
Venkat,
There is another way to do this. If you have a category of "thing" you are
attempting to filter over, then you create a query and tag the documents
with this category. So, create a 'categories' field and append 'thing' to
the field updating the field if need be. (Be wary of over generat
On 5/30/2019 4:13 PM, Venkateswarlu Bommineni wrote:
Thank you guys for quick response.
I was able to query solr by sending 1500 products using solrJ with http
post method.
But I had to change maxBooleanClauses to 4096 from default 1024.
But I wanted to check with you guys that, will there be
Thank you guys for quick response.
I was able to query solr by sending 1500 products using solrJ with http
post method.
But I had to change maxBooleanClauses to 4096 from default 1024.
But I wanted to check with you guys that, will there be any performance
issues by changing maxBooleanClauses to
On 5/30/2019 2:20 PM, Venkateswarlu Bommineni wrote:
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.
You'll probably want to send that as a POST, wh
You can use POST instead of GET.
But you may also want to see if you can refactor those 1500 strings somehow.
If you don't use it already, maybe Terms query parser could be useful:
https://lucene.apache.org/solr/guide/7_7/other-parsers.html#terms-query-parser
Also, if at least some of those numb
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.
