You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@atlas.apache.org by "Sarath Subramanian (JIRA)" <ji...@apache.org> on 2019/07/03 04:47:00 UTC

[jira] [Updated] (ATLAS-3314) Update relationshipCategory between spark_table and spark_storagedesc type

     [ https://issues.apache.org/jira/browse/ATLAS-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sarath Subramanian updated ATLAS-3314:
--------------------------------------
    Summary: Update relationshipCategory between spark_table and spark_storagedesc type  (was: Update the relationship between spark_table and spark_storagedesc)

> Update relationshipCategory between spark_table and spark_storagedesc type
> --------------------------------------------------------------------------
>
>                 Key: ATLAS-3314
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3314
>             Project: Atlas
>          Issue Type: Task
>          Components: atlas-intg
>    Affects Versions: 2.0.0
>            Reporter: Jungtaek Lim
>            Assignee: Sarath Subramanian
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Spark models define the relationship of "spark_table" and "spark_storagedesc" as "COMPOSITION", which requires "spark_storagedesc" to refer "spark_table". (Note that Atlas 1.x didn't require in same relationship.)
> This enforces the sequence of creating entities (as Atlas doesn't support referring other entity in same creation request) to "spark_table" -> "spark_storagedesc", which doesn't seem to work in every usages, at least this requires major changes on Spark Atlas Connector.
> As a workaround, we can loosen the relationship via defining the relationship as "ASSOCIATION", so that they can refer each other at any side.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)