Hello, Dmitri.
You can try to use segmented caches which are more realtime.
it should work like q={!parent which=COLOR:Blue v=''} instead of q=
COLOR:Blue
Make sure you have the following definition in solrconfig.xml this
regenerator should transfer filter bitsets between searchers.
It
Had this typed up yesterday and forgot to send.
"Is there no way to ensure that the top level filter caches are not
expunged when some documents are added to the index and have the
changes available at the same time?"
no. And it's not something that you can do without major architectural
changes.
On 4/23/2018 11:56 PM, Papa Pappu wrote:
> I've written down my query over stack-overflow. Here is the link for that :
> https://stackoverflow.com/questions/49993681/preventing-solr-cache-flush-when-commiting
>
> In short, I am facing troubles maintaining my solr caches when commits
> happen and th
>From memory try the following:
Don't manually commit from client after batch indexing
set soft commit to be a a long time interval. As long as acceptable to run
stale, say 5 mins or longer if you can.
set hard commit to be short (seconds ) to keep everything neat and tidy
regards updates and avo
Hi,
I've written down my query over stack-overflow. Here is the link for that :
https://stackoverflow.com/questions/49993681/preventing-solr-cache-flush-when-commiting
In short, I am facing troubles maintaining my solr caches when commits
happen and the question provides detailed description of th
