Improve exception handling in cache.asMap().computeIfAbsent
etc.
#7980
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Improve exception handling in
cache.asMap().computeIfAbsent
etc.Don't store an exception thrown by the compute function. It doesn't appear that the stored exception is ever used. Tests still pass after this deletion.
Also move the evaluation of the compute function to before the possible creation of a new entry, so if it throws an exception then no entry is created.
Fixes #5438, fixes #7625, fixes #7975.
RELNOTES=Handling of exceptions from compute functions in
Cache.asMap().computeIfAbsent
and the like has been improved. (We do still recommend using Caffeine rather thancom.google.common.cache
.)