[ATLAS-3193] Import Service: Importing to Existing Database Fails

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: trunk
• Fix Version/s: trunk
• Component/s: atlas-core
• Assignee: Ashutosh Mestry
• Reporter: Ashutosh Mestry
• Due: 10/May/19
• Created: 06/May/19 23:20
• Updated: 08/May/19 16:27
• Resolved: 08/May/19 16:27

Description

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.