Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.0.0, trunk
-
None
Description
Background
In versions prior to v1.0, it was possible to have entity types that contained attributes with classification as their type.
In v1.0 creation of such types is not supported.
The impact is that data migration fails during AtlasTypesDef (atlas-migration-typesdef.json attached_)_ import with this error:
org.apache.atlas.exception.AtlasBaseException: createComplexTraitTypeTestprayivofx4.complexTrait: invalid attribute type. Attribute cannot be of type classification
Solution
Given the type mentioned is no longer supported, the solution would be to build a new type that mimics the old type so that data is moved correctly.
Approach:
- Create a AtlasStructDef with a classification name prefixed with legacy.
- Use the new type as the type of the attribute.
- During edge import, modify the edge label such that it is pointing to a struct rather than a classification.
Attachments
Attachments
Issue Links
- links to