[
https://issues.apache.org/jira/browse/SOLR-15555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17389056#comment-17389056
]
Ben Manes commented on SOLR-15555:
----------------------------------
Those are all available and can be accessed through the
{{AsyncCache.synchronous()}} view. There is also an {{asMap()}} view at both
levels, depending on if you want future or concrete values (with sync handling
more complexity around joining and computes). For example
{{Cache.invalidate(key)}} return {{void}} so it is cost equivalent to
{{AsyncCache.asMap().remove(key)}} which returns {{CompleteableFuture<V>}},
whereas {{AsyncCache.synchronous().asMap().remove(key)}} returns {{V}} so it
must block until the future is done.
> Use filterCache.computeIfAbsent in SolrIndexSearcher
> ----------------------------------------------------
>
> Key: SOLR-15555
> URL: https://issues.apache.org/jira/browse/SOLR-15555
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mike Drob
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> When multiple concurrent queries come in at the same time, in several cases
> they can trigger concurrent computations of a DocSet for the cache. We should
> investigate where this happens and possibly take care to only do a single
> computation when possible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
