Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.0.0, trunk
-
None
Description
Background
During migration import (and regular Import) types coming in are processed in the following way:
- New types are determined.
- Modification to existing types are determined.
Steps to Duplicate
Pre-requisites:
- Create type definition with new structDef.
- Modify hive_table (existing) such a new attribute references the structDef.
Steps
- Initiate migration import.
Expected outcome
- New types should be part of the types definition (using REST APIs and property pages).
- Data should get migrated.
Actual outcome
- Type definition import fails.
Additional information
Stack trace:
org.apache.atlas.exception.AtlasBaseException: Given typename hive_table_profile_data was invalid at org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.tryUpdateByName(AtlasTypeDefGraphStore.java:1025) at org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateEntityDefByName(AtlasTypeDefGraphStore.java:285) at org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$$FastClassBySprin
PC build: https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1533/