The second approach (newSearcher listener) is a nice approach if the filter
cache is too full to rely on auto-warming.
Static warming queries fail on cross core joins but I believe succeed on a
self core join. So you could move the inventory into the same core and use
a static warming query. The do
What is this warning message?
Regardless, bin/solr could detect that this scenario is going to occur and
print a message of its own so that users have better context on the
situation.
In other ways, we are investing in securing Solr. Modularization comes to
my mind first. And I really wish for a
I'm not sure there is a clean/simple solution to this specific problem.
But I could imagine a more general & simple feature that could solve this
scenario, with just a bit more work by the user.
Imagine an optional cache-key on ExtendedQuery auto-parsed, perhaps with
local-param "cacheKey". It wo
