[APEXMALHAR-2473] Support for global cache meta information in db CacheManager

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.8.0
• Assignee: Oliver Winke
• Reporter: Pramod Immaneni
• Created: 04/Apr/17 04:31
• Updated: 11/Nov/17 11:25
• Resolved: 18/May/17 20:43

Description

Currently db CacheManager has no knowledge of characteristics of the data or the cache stores, so it handles all scenarios uniformly. This may not be the optimal implementation in all cases. Better optimizations can be performed in the manager if this information is known. A few examples, if the data is read-only the keys in the primary cache need not be refreshed like they are being done daily today, if the primary cache size is known the number of initial entries loaded from backup needn't exceed it. Add support for such general cache meta information in the manager.

Issue Links

• links to: GitHub Pull Request #605

Sub-Tasks

• FSLoader only returns value at the beginning: Closed
• CacheStore needn't expire data if it read-only data: Closed