Details
-
Bug
-
Status: Patch Available
-
Major
-
Resolution: Unresolved
-
1.1.0
-
None
Description
Following is the test scenario:
In the source cluster :
1. create table with 3 columns (id,name,dob)
2. drop column dob
3. add the same dob column again.
Now table has 3 ACTIVE columns and 1 DELETED column.
Export the db into the target cluster.
In the target cluster :
only 2 ACTIVE (id,name) and 1 DELETED (dob) column is present. The ACTIVE column (dob) is not present.
The exported zip contains both the DELETED and the ACTIVE dob column entity.
In the source cluster ,
if GUID1 is GUID of ACTIVE dob entity , and GUID2 is GUID of deleted dob entity.
In the target cluster ,
GUID1 is GUID of DELETED entity.
Example :
In source :
ACTIVE: https://atlas_source_host/index.html#!/detailPage/7cca7064-8519-4db3-aab5-ebd446d15070
DELETED:https:// atlas_source_host /index.html#!/detailPage/f7686214-7585-4da3-875f-3e5223875289
In target :
DELETED : https:// atlas_target_host /index.html#!/detailPage/7cca7064-8519-4db3-aab5-ebd446d15070
Entity with GUID f7686214-7585-4da3-875f-3e5223875289 is not found.
Attachments
Attachments
Issue Links
- links to