fix(cache2k): create unbounded cache if maxSize is not specified #184
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.
When
ICacheSpec#maxSize
yields null, an unbounded cache should be created. By default, cache2k imposes anentryCapacity
of 1802 (rather than creating an unbounded cache). As a result, we specifyLong.MAX_VALUE
to create an unbounded cache whenmaxSize
is null, in accordance to the Xanthic spec.https://cache2k.org/docs/latest/apidocs/cache2k-api/org/cache2k/Cache2kBuilder.html#entryCapacity(long)