[ https://issues.apache.org/jira/browse/ATLAS-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342283#comment-15342283 ]
David Kantor commented on ATLAS-856: ------------------------------------ [~shwethags] Yes your changes make sense, good idea to use Configuration and mutate the property setting needed for the tests. I noticed your patch does a delete and add of classes that I renamed. Rather than lose the history of those renamed modules, I will apply your changes in my source, and upload a new set of changes to review board and attach an updated. That way the renames will be recorded in git correctly. Thanks very much for your help on this. > Lazy-load type cache provider > ----------------------------- > > Key: ATLAS-856 > URL: https://issues.apache.org/jira/browse/ATLAS-856 > Project: Atlas > Issue Type: New Feature > Reporter: David Kantor > Assignee: David Kantor > Attachments: ATLAS-856.patch, rb48565.patch > > > A modified version of the default local cache provider which will run a > lookup on the backend storage if a requested type is not found in the cache, > and load it in the cache and return it if it's found. This lazy-loading cache > would cover the case where new types are registered, not the case where > existing types are modified, while avoiding the deployment/maintenance and > performance impact of a distributed cache in an HA environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)