[
https://issues.apache.org/jira/browse/ATLAS-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Kantor updated ATLAS-856:
-------------------------------
Description: 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. (was: 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, or raise an
exception if not. 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.)
> 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: 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)
