[
https://issues.apache.org/jira/browse/ATLAS-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Mestry updated ATLAS-3193:
-----------------------------------
Attachment: ATLAS-3193-Import-to-Existing.patch
> Import Service: Importing to Existing Database Fails
> ----------------------------------------------------
>
> Key: ATLAS-3193
> URL: https://issues.apache.org/jira/browse/ATLAS-3193
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: trunk
> Reporter: Ashutosh Mestry
> Assignee: Ashutosh Mestry
> Priority: Major
> Fix For: trunk
>
> Attachments: ATLAS-3193-Import-to-Existing.patch
>
>
> *Background*
> Existing implementation of import assumes that the top-level entity is absent
> in the server that it is importing to.
> Users create a place holder entity and then attempt an import. This results
> in failure to import.
> *Steps to Duplicate*
> * From beeline: _create database stocks;_ From Atlas ensure that _hive_db_
> with _qualifiedName:_ _stocks@cl1_ is created.
> * Import stocks database (from _/repository/src/test/resources/stocks.zip_).
> *_Expected Results_*
> Import will be performed successfully.
> *_Actual Results_*
> Import fails with exception.
> *Solution Guidance*
> * Before starting import, check existence of top-level entities on the
> server.
> * If top-level entity exists, update its GUID with the one from incoming
> entity. Preserve the changed guid a new field say ___historicalGuids_.
> * If none exist, proceed normally.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
