[jira] [Updated] (ATLAS-2888) Export & Import Process: Change Marker Removed Inadvertently
[
https://issues.apache.org/jira/browse/ATLAS-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carol Drummond updated ATLAS-2888:
--
Labels: (was: release-notes)
> Export & Import Process: Change Marker Removed Inadvertently
>
>
> Key: ATLAS-2888
> URL: https://issues.apache.org/jira/browse/ATLAS-2888
> Project: Atlas
> Issue Type: Bug
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-2888-Change-marker-fix-for-server-name.2.patch,
> ATLAS-2888-REPL_DETAILS-entry-missing.patch
>
>
> *Background*
> When using _replicatedTo_ and _replicatedFrom_ options in _Export_ and
> _Import_ requests, the _AtlasServer_ stores a marker indicating the next
> starting point for export to being.
> *Steps to Duplicate*
> * Setup _export-options.json_ as follows:
> {{_{_}}{{_"itemsToExport": [_}}{{_{ "typeName": "hive_db",
> "uniqueAttributes": \{ "qualifiedName": "stocks@cl1"
> }}_}}{{_],_}}{{_"options": {_}}{{_"fetchType":
> "incremental",_}}{{_"skipLineage": true,_}}{{_"changeMarker":
> 0,_}}{{_"replicatedTo": "SFO$clMain"_}}{{_}_}}{{_}_}} * Perform export using
> Export REST calls.
> * Update _export-options.json_ with the _changeMarker_ from the _Atlas'
> application.log._
> * Notice the _AtlasServer_ entry for _clMain_. It is updated with
> _changeMarker_ value from log.
> * Perform export using Export REST API.
> * Export will happen with no entities exported (since nothing was changed in
> the database). Atlas' application.log indicates new change maker.
> _Expected results:_ _AtlasServer_ for _clMain_ should continue displaying
> _REPL_DETAILS_ entry.
> _Observed results:_ _AtlasServer_ _for_ _clMain_ displays properties with
> _REPL_DETAILS_ entry removed.
> *Root Cause*
> Within _AuditsWriter_, the entry for _clMain_ is saved 2 times. First without
> the change marker and then if export operation has entities exported, the
> server entity is saved with the change marker.
> If no entities, exist the server entry remains without the _REPL_DETAILS_
> entry present.
> *Possible Fix*
> Save the target server entry only once.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-2888) Export & Import Process: Change Marker Removed Inadvertently
[
https://issues.apache.org/jira/browse/ATLAS-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carol Drummond updated ATLAS-2888:
--
Labels: release-notes (was: )
> Export & Import Process: Change Marker Removed Inadvertently
>
>
> Key: ATLAS-2888
> URL: https://issues.apache.org/jira/browse/ATLAS-2888
> Project: Atlas
> Issue Type: Bug
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Labels: release-notes
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-2888-Change-marker-fix-for-server-name.2.patch,
> ATLAS-2888-REPL_DETAILS-entry-missing.patch
>
>
> *Background*
> When using _replicatedTo_ and _replicatedFrom_ options in _Export_ and
> _Import_ requests, the _AtlasServer_ stores a marker indicating the next
> starting point for export to being.
> *Steps to Duplicate*
> * Setup _export-options.json_ as follows:
> {{_{_}}{{_"itemsToExport": [_}}{{_{ "typeName": "hive_db",
> "uniqueAttributes": \{ "qualifiedName": "stocks@cl1"
> }}_}}{{_],_}}{{_"options": {_}}{{_"fetchType":
> "incremental",_}}{{_"skipLineage": true,_}}{{_"changeMarker":
> 0,_}}{{_"replicatedTo": "SFO$clMain"_}}{{_}_}}{{_}_}} * Perform export using
> Export REST calls.
> * Update _export-options.json_ with the _changeMarker_ from the _Atlas'
> application.log._
> * Notice the _AtlasServer_ entry for _clMain_. It is updated with
> _changeMarker_ value from log.
> * Perform export using Export REST API.
> * Export will happen with no entities exported (since nothing was changed in
> the database). Atlas' application.log indicates new change maker.
> _Expected results:_ _AtlasServer_ for _clMain_ should continue displaying
> _REPL_DETAILS_ entry.
> _Observed results:_ _AtlasServer_ _for_ _clMain_ displays properties with
> _REPL_DETAILS_ entry removed.
> *Root Cause*
> Within _AuditsWriter_, the entry for _clMain_ is saved 2 times. First without
> the change marker and then if export operation has entities exported, the
> server entity is saved with the change marker.
> If no entities, exist the server entry remains without the _REPL_DETAILS_
> entry present.
> *Possible Fix*
> Save the target server entry only once.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-2888) Export & Import Process: Change Marker Removed Inadvertently
[
https://issues.apache.org/jira/browse/ATLAS-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian updated ATLAS-2888:
--
Fix Version/s: 2.0.0
1.2.0
> Export & Import Process: Change Marker Removed Inadvertently
>
>
> Key: ATLAS-2888
> URL: https://issues.apache.org/jira/browse/ATLAS-2888
> Project: Atlas
> Issue Type: Bug
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-2888-Change-marker-fix-for-server-name.2.patch,
> ATLAS-2888-REPL_DETAILS-entry-missing.patch
>
>
> *Background*
> When using _replicatedTo_ and _replicatedFrom_ options in _Export_ and
> _Import_ requests, the _AtlasServer_ stores a marker indicating the next
> starting point for export to being.
> *Steps to Duplicate*
> * Setup _export-options.json_ as follows:
> {{_{_}}{{_"itemsToExport": [_}}{{_{ "typeName": "hive_db",
> "uniqueAttributes": \{ "qualifiedName": "stocks@cl1"
> }}_}}{{_],_}}{{_"options": {_}}{{_"fetchType":
> "incremental",_}}{{_"skipLineage": true,_}}{{_"changeMarker":
> 0,_}}{{_"replicatedTo": "SFO$clMain"_}}{{_}_}}{{_}_}} * Perform export using
> Export REST calls.
> * Update _export-options.json_ with the _changeMarker_ from the _Atlas'
> application.log._
> * Notice the _AtlasServer_ entry for _clMain_. It is updated with
> _changeMarker_ value from log.
> * Perform export using Export REST API.
> * Export will happen with no entities exported (since nothing was changed in
> the database). Atlas' application.log indicates new change maker.
> _Expected results:_ _AtlasServer_ for _clMain_ should continue displaying
> _REPL_DETAILS_ entry.
> _Observed results:_ _AtlasServer_ _for_ _clMain_ displays properties with
> _REPL_DETAILS_ entry removed.
> *Root Cause*
> Within _AuditsWriter_, the entry for _clMain_ is saved 2 times. First without
> the change marker and then if export operation has entities exported, the
> server entity is saved with the change marker.
> If no entities, exist the server entry remains without the _REPL_DETAILS_
> entry present.
> *Possible Fix*
> Save the target server entry only once.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2888) Export & Import Process: Change Marker Removed Inadvertently
[
https://issues.apache.org/jira/browse/ATLAS-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Mestry updated ATLAS-2888:
---
Attachment: ATLAS-2888-Change-marker-fix-for-server-name.2.patch
> Export & Import Process: Change Marker Removed Inadvertently
>
>
> Key: ATLAS-2888
> URL: https://issues.apache.org/jira/browse/ATLAS-2888
> Project: Atlas
> Issue Type: Bug
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-2888-Change-marker-fix-for-server-name.2.patch,
> ATLAS-2888-REPL_DETAILS-entry-missing.patch
>
>
> *Background*
> When using _replicatedTo_ and _replicatedFrom_ options in _Export_ and
> _Import_ requests, the _AtlasServer_ stores a marker indicating the next
> starting point for export to being.
> *Steps to Duplicate*
> * Setup _export-options.json_ as follows:
> {{_{_}}{{_"itemsToExport": [_}}{{_{ "typeName": "hive_db",
> "uniqueAttributes": \{ "qualifiedName": "stocks@cl1"
> }}_}}{{_],_}}{{_"options": {_}}{{_"fetchType":
> "incremental",_}}{{_"skipLineage": true,_}}{{_"changeMarker":
> 0,_}}{{_"replicatedTo": "SFO$clMain"_}}{{_}_}}{{_}_}} * Perform export using
> Export REST calls.
> * Update _export-options.json_ with the _changeMarker_ from the _Atlas'
> application.log._
> * Notice the _AtlasServer_ entry for _clMain_. It is updated with
> _changeMarker_ value from log.
> * Perform export using Export REST API.
> * Export will happen with no entities exported (since nothing was changed in
> the database). Atlas' application.log indicates new change maker.
> _Expected results:_ _AtlasServer_ for _clMain_ should continue displaying
> _REPL_DETAILS_ entry.
> _Observed results:_ _AtlasServer_ _for_ _clMain_ displays properties with
> _REPL_DETAILS_ entry removed.
> *Root Cause*
> Within _AuditsWriter_, the entry for _clMain_ is saved 2 times. First without
> the change marker and then if export operation has entities exported, the
> server entity is saved with the change marker.
> If no entities, exist the server entry remains without the _REPL_DETAILS_
> entry present.
> *Possible Fix*
> Save the target server entry only once.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2888) Export & Import Process: Change Marker Removed Inadvertently
[
https://issues.apache.org/jira/browse/ATLAS-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Mestry updated ATLAS-2888:
---
Attachment: ATLAS-2888-REPL_DETAILS-entry-missing.patch
> Export & Import Process: Change Marker Removed Inadvertently
>
>
> Key: ATLAS-2888
> URL: https://issues.apache.org/jira/browse/ATLAS-2888
> Project: Atlas
> Issue Type: Bug
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-2888-REPL_DETAILS-entry-missing.patch
>
>
> *Background*
> When using _replicatedTo_ and _replicatedFrom_ options in _Export_ and
> _Import_ requests, the _AtlasServer_ stores a marker indicating the next
> starting point for export to being.
> *Steps to Duplicate*
> * Setup _export-options.json_ as follows:
> {{_{_}}{{_"itemsToExport": [_}}{{_{ "typeName": "hive_db",
> "uniqueAttributes": \{ "qualifiedName": "stocks@cl1"
> }}_}}{{_],_}}{{_"options": {_}}{{_"fetchType":
> "incremental",_}}{{_"skipLineage": true,_}}{{_"changeMarker":
> 0,_}}{{_"replicatedTo": "SFO$clMain"_}}{{_}_}}{{_}_}} * Perform export using
> Export REST calls.
> * Update _export-options.json_ with the _changeMarker_ from the _Atlas'
> application.log._
> * Notice the _AtlasServer_ entry for _clMain_. It is updated with
> _changeMarker_ value from log.
> * Perform export using Export REST API.
> * Export will happen with no entities exported (since nothing was changed in
> the database). Atlas' application.log indicates new change maker.
> _Expected results:_ _AtlasServer_ for _clMain_ should continue displaying
> _REPL_DETAILS_ entry.
> _Observed results:_ _AtlasServer_ _for_ _clMain_ displays properties with
> _REPL_DETAILS_ entry removed.
> *Root Cause*
> Within _AuditsWriter_, the entry for _clMain_ is saved 2 times. First without
> the change marker and then if export operation has entities exported, the
> server entity is saved with the change marker.
> If no entities, exist the server entry remains without the _REPL_DETAILS_
> entry present.
> *Possible Fix*
> Save the target server entry only once.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
