[
https://issues.apache.org/jira/browse/ATLAS-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16583365#comment-16583365
]
ASF subversion and git services commented on ATLAS-2814:
--------------------------------------------------------
Commit b9aa6d5d36191544174cdd7ee97cda4474aa2ca8 in atlas's branch
refs/heads/branch-0.8 from [~ashutoshm]
[ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=b9aa6d5 ]
ATLAS-2814: Cluster stores replication details.
> Export & Import Process: Add Data to AtlasCluster About Last Successful Import
> ------------------------------------------------------------------------------
>
> Key: ATLAS-2814
> URL: https://issues.apache.org/jira/browse/ATLAS-2814
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
> Affects Versions: 0.8.3
> Reporter: Ashutosh Mestry
> Assignee: Ashutosh Mestry
> Priority: Major
> Fix For: 0.8.3
>
> Attachments: ATLAS-2814-Cluster-stores-replication-details.patch
>
>
> *Background*
> Scenario: Couple of Atlas clusters are setup such that incremental export and
> import is setup via some custom program. Example, Cluster _cl1_ exports does
> incremental export and the output is imported into cluster _cl2_.
> It may be worth while to maintain some information about the last successful
> import. This way the next incremental export will have correct parameters for
> its export.
> *Approach Guidance*
> * Create a new model, say _AtlasSyncInfo_, that stores information about top
> level entity used for export and the timestamp that should be used for
> subsequent incremental export.
> * Utilize _AtlasCluster_'s _additionalInfo_ fields to store serialized
> version of _AtlasSyncInfo_.
> * Provide REST APIs for retrieval of this information.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
