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.
<query>
<cache name="perSegFilter"
class="solr.LRUCache"
size="100"
initialSize="10"
autowarmCount="100%"
regenerator="solr.NoOpRegenerator"/>
</query>
It make sense to check this cache right after commit.
On Tue, Apr 24, 2018 at 8:56 AM, Papa Pappu <tuhaipa...@gmail.com> wrote:
> 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 the same.
>
> Based on my use-case if someone can recommend what settings I should use or
> practices I should follow it'll be really helpful.
>
> Thanks and regards,
> Dmitri
>
--
Sincerely yours
Mikhail Khludnev
