It occurs to me that this mail itself is potentially spam advertising. Note:
1) Attempt to create fear (oh no I have a broken link, or a server problem)
to get attention and then transition to unrelated request
2) Inclusion of a mention of a *commercial* web site
3) The request clearly doesn't mak
SOLR-15428: Integrating the jmh micro-benchmark tool into the build
I want to bring attention to this issue, because there is lots to drop in
on top of it, but a bit like JUnit tests, it’s best if you get things close
to as wanted early for consistency without having to change a ton of tests
as y
If Caffeine is being used, it might be worthwhile to look into using it’s
feature set to do this.
It has the ability to do either async or sync loading - if using sync,
modifications will block while an entry is loading.
It also has has a bulk load API, might be interesting for things like auto
w
Thanks for the pointer, David!
While browsing through that issue, I found this comment left by you
from SOLR-14166
https://github.com/apache/solr/blob/main/solr/core/src/java/org/apache/solr/search/SolrIndexSearcher.java#L1185
"note: can't use computeIfAbsent because can be recursive"
I don't q
Ishan responded to you 4 days ago:
https://lists.apache.org/thread.html/r6b65eebb4b2b3d724f8ef91e0587ebebf75effe72444b3d709de7905%40%3Cdev.solr.apache.org%3E
This is a mailing list, and thus responses go to the list and then from the
list to you, and not directly from a respondent to you. Perhaps
Ideally, we could use SolrCache.computeIfAbsent [1] for the filter cache,
as is used for some of the other caches. The best SolrCache is
CaffeineCache which works atomically for the same key (just as does
ConcurrentHashMap). The problem is that this method on CaffeineCache does
not support comput
Hi!I hope you're having a great day!Did you have a chance to see my previous message?Please let me know what you think.Thanks and have a wonderful day!On Friday, July 9, 2021 8:25 PM, wrote:> Hi!> > I was suggested to contact you regarding some issues I had on your website.> I ran across your res
On 7/13/2021 2:30 PM, Mike Drob wrote:
One option that I've thought about is if instead of inserting results
into the cache directly, we pre-register a future in the cache, and
then use that as a reference to the results. Multiple queries coming
in parallel would all wait for the same result ca
