[
https://issues.apache.org/jira/browse/ATLAS-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Padovani updated ATLAS-2178:
-----------------------------------
Attachment: entities.json
rel1.json
rel2.json
rel3.json
rel4.json
rel5.json
types.json
types.json is the type system, while entities.json are the new entities
created. Each of the rel#.json files contains the payload to create a
relationship. The guids in the relationship#.json files have to be updated to
match the created entities prior to submission.
Results seen from these files:
SorTable instance does not know about linked column, column doesn't know about
table.
SorExtraction (Process) only has outputs set, but no inputs.
Many other inconsistencies in how relationships were set including the legacy
attributes not being set correctly.
> Type Inheritance in conjunction with RelationshipDef fails to set legacy
> attributes
> -----------------------------------------------------------------------------------
>
> Key: ATLAS-2178
> URL: https://issues.apache.org/jira/browse/ATLAS-2178
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 1.0.0
> Reporter: Pierre Padovani
> Attachments: entities.json, rel1.json, rel2.json, rel3.json,
> rel4.json, rel5.json, types.json
>
>
> If a type inherits from another that has an old style reference attribute,
> and a new style RelationshipDef defined, creating the relationship instance
> fails to set the legacy attributes and in some cases fails to create the
> relationship itself.
> Steps to reproduce:
> * create a type, say my_table, that inherits from the hive_table
> * Create an instance of the new type my_table
> * Create an instance of a hive_column
> * Create the containment relationship between the two models.
> This behavior causes odd and inconsistent behavior and fully breaks lineage
> reports for process types that inherit from the built in Process.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
