Re: FilterQueries with NRT

You can experiment with the backdoor NRT filters: - replace COLOR:Red to {!parent which='COLOR:Red' v=''} - add *NoOpRegenerator **into perSegFilter* *- **monitor cache stats. * On Fri, May 11, 2018 at 10:46 PM, root23 wrote: > Hi all, > We have a requirement for NRT

Re: FilterQueries with NRT

bq. does it make even sense to cache anything In a word, "no". Now only would I set the cache entry size to zero, I'd form my filer queries with {!cache=false}... There's no particular point in computing the entire cache entry in this case, possibly even with a cost=101. See:

FilterQueries with NRT

Hi all, We have a requirement for NRT search. Our autosoft commit time is set to 500 ms(i know its low.But that's another story). We use filter queries extensively for most of our queries. But i am trying to understand how filter query caching works with NRT. Now as i understand we use fq for