You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Sarath Subramanian (JIRA)" <ji...@apache.org> on 2019/04/19 19:04:00 UTC
[jira] [Updated] (ATLAS-2886) Export & Import Process: Add Support
for Qualified Cluster Names
[ https://issues.apache.org/jira/browse/ATLAS-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sarath Subramanian updated ATLAS-2886:
--------------------------------------
Fix Version/s: 1.2.0
> Export & Import Process: Add Support for Qualified Cluster Names
> ----------------------------------------------------------------
>
> Key: ATLAS-2886
> URL: https://issues.apache.org/jira/browse/ATLAS-2886
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
> Affects Versions: 0.8.2
> Reporter: Ashutosh Mestry
> Assignee: Ashutosh Mestry
> Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0
>
> Attachments: ATLAS-2886-Export-Import-Support-fully-qualified-ser.patch
>
>
> *Background*
> For cases where cluster same cluster names can exist in different data centers, it helps to add a data center name as prefix to cluster name.
> The _replicatedTo_ and _replicatedFrom_ attributes in _AtlasExportRequest_ and _AtlasImportRequest_ should be the place to specify this.
> *Approach Guidance*
> * Follow a convention where _data center name_ and cluster name should be separated by $. E.g. _dc1$cl1_
> * Modify _AuditsWriter_ to support this.
> * _AtlasServer_ already has _qualifiedName_ as a field. This will hold the fully qualified name.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)