Ashutosh Mestry created ATLAS-3212:
--------------------------------------
Summary: Import Service: Importing to Existing Database with
Different Name
Key: ATLAS-3212
URL: https://issues.apache.org/jira/browse/ATLAS-3212
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: trunk
Reporter: Ashutosh Mestry
Assignee: Ashutosh Mestry
Fix For: trunk
*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*
# From an instance of Atlas, export _hive_db_ with name say stocks and few
tables, say _t1_ and _t2_.
# On a fresh instance of Atlas, via beeline create _hive_db_ with no tables
with name say _stocks_t1._
# 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
