[ATLAS-3212] Import Service: Importing to Existing Database with Different Name

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0, trunk
• Fix Version/s: trunk
• Component/s: atlas-core
• Assignee: Ashutosh Mestry
• Reporter: Ashutosh Mestry
• Created: 15/May/19 19:52
• Updated: 24/May/19 17:59
• Resolved: 24/May/19 17:59

Description

Background

ATLAS-3193 added support to existing hive_db entity. The implementation did not account for transform applied to the import where the target database was renamed.

Steps to Duplicate

1. From an instance of Atlas, export hive_db with name say stocks and few tables, say t1 and t2.
2. On a fresh instance of Atlas, via beeline create hive_db with no tables with name say stocks_t1.
3. Perform an import of the zip from step 1 with an import transform that renames db name.

Expected Results: Import should populate tables t1 and t2 to stocks_t1.

Actual Results: Import fails with an AtlasSchemaViolation exception as it attempts to overwrite existing db whose GUID differs.

Solution Guidance

• Import operation should handle AtlasSchemaViolation exception and update the GUID. The the implementation where it processes export request attempting to find starting entities is thus not relevant anymore.