[
https://issues.apache.org/jira/browse/ATLAS-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625169#comment-16625169
]
ASF subversion and git services commented on ATLAS-2886:
--------------------------------------------------------
Commit ba717c6e4bdfc9e9d59698ac150d8f12efe3e56e in atlas's branch
refs/heads/branch-0.8 from [~ashutoshm]
[ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=ba717c6 ]
ATLAS-2886: Support for fully qualified server name
Signed-off-by: Madhan Neethiraj <mad...@apache.org>
> 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
>
> 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)
