More fully support LRU caching for EntityGroups and EntityRelations. #122
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.
This provides a middle ground for applications with large relations and entity groups so they don't need to be fully cached (using all that heap space) but can still benefit from LRU caching and otherwise be used similar to when cached and get CacheMessageManager updates appropriately.
Note that for both LruCacheGroup and LruSqlEntityRelation, client code will want to continue to avoid operations that result in reading the full table into memory. These changes enable an application to treat these closer to their fully-cached counterparts, but client code must still beware of the performance consequences of an LruCacheGroup.list() or LruSqlEntityRelation.replaceAll() or removeAll().