[jira] [Updated] (ATLAS-2814) Export & Import Process: Add Data to AtlasCluster About Last Successful Import
[ https://issues.apache.org/jira/browse/ATLAS-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2814: -- Labels: (was: release-notes) > 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, 1.2.0, 2.0.0 > > 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 (v8.3.4#803005)
[jira] [Updated] (ATLAS-2814) Export & Import Process: Add Data to AtlasCluster About Last Successful Import
[ https://issues.apache.org/jira/browse/ATLAS-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2814: -- Labels: release-notes (was: ) > 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 > Labels: release-notes > Fix For: 0.8.3, 1.2.0, 2.0.0 > > 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 (v8.3.4#803005)
[jira] [Updated] (ATLAS-2814) Export & Import Process: Add Data to AtlasCluster About Last Successful Import
[ https://issues.apache.org/jira/browse/ATLAS-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-2814: -- Fix Version/s: 2.0.0 1.2.0 > 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, 1.2.0, 2.0.0 > > 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)
[jira] [Updated] (ATLAS-2814) Export & Import Process: Add Data to AtlasCluster About Last Successful Import
[ https://issues.apache.org/jira/browse/ATLAS-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-2814: --- Attachment: ATLAS-2814-Cluster-stores-replication-details.patch > 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)
[jira] [Updated] (ATLAS-2814) Export & Import Process: Add Data to AtlasCluster About Last Successful Import
[ https://issues.apache.org/jira/browse/ATLAS-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-2814: --- Description: *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. was: *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. > 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 > > > *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)
