[
https://issues.apache.org/jira/browse/ATLAS-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Mestry updated ATLAS-2717:
-----------------------------------
Attachment: ATLAS-2717-Handling-legacy-types-that-reference-clas.patch
> Data Migration: Importing Entity with Attribute of Classification Type from
> pre-v1.0
> ------------------------------------------------------------------------------------
>
> Key: ATLAS-2717
> URL: https://issues.apache.org/jira/browse/ATLAS-2717
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: trunk, 1.0.0
> Reporter: Ashutosh Mestry
> Assignee: Ashutosh Mestry
> Priority: Major
> Fix For: trunk
>
> Attachments:
> ATLAS-2717-Handling-legacy-types-that-reference-clas.patch,
> atlas-migration-typesdef.json
>
>
> *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:
> {code:java}
> org.apache.atlas.exception.AtlasBaseException:
> createComplexTraitTypeTestprayivofx4.complexTrait: invalid attribute type.
> Attribute cannot be of type classification
> {code}
> *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.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
