[
https://issues.apache.org/jira/browse/ATLAS-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16698380#comment-16698380
]
Madhan Neethiraj commented on ATLAS-2948:
-----------------------------------------
[~nadenf] - its not clear what the advantages (or use cases) are for a
pluggable caching of TypeDef cache and RequestContext cache. Can you please add
details? Also, if you have a patch to address this, please create a review
request at https://reviews.apache.org.
> Cache implementations should be consistent and configurable
> -----------------------------------------------------------
>
> Key: ATLAS-2948
> URL: https://issues.apache.org/jira/browse/ATLAS-2948
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
> Affects Versions: trunk
> Reporter: Franco
> Priority: Major
>
> Throughout Apache Atlas caches are hardcoded. For example:
> (1) AtlasTypeRegistry has a TypeDef cache which is a ConcurrentHashMap
> (2) RequestContext has an entity cache which is a Map
>
> Instead there should be a standardised Cache implementation across the board
> that is pluggable so that users can try a different approach e.g. use Redis
> to help with Atlas outages. Or maybe something like Ignite to allow for Atlas
> to be clustered.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
