[
https://issues.apache.org/jira/browse/APEXMALHAR-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15954555#comment-15954555
]
Pramod Immaneni commented on APEXMALHAR-2473:
---------------------------------------------
The CacheManager can allow the user to specify this meta information via
properties. It can then use this information to perform optimal processing. It
can also pass this meta information to the primary and backup stores so they
can perform the necessary optimization as well. The component interface can be
used to initialize and pass this information to the stores.
> Support for global cache meta information in db CacheManager
> ------------------------------------------------------------
>
> Key: APEXMALHAR-2473
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2473
> Project: Apache Apex Malhar
> Issue Type: Improvement
> Reporter: Pramod Immaneni
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
