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

Madhan Neethiraj updated ATLAS-2372:
------------------------------------
    Affects Version/s: 1.0.0
        Fix Version/s: 1.0.0

> Export-Import: Support for Relationship Attributes Missing
> ----------------------------------------------------------
>
>                 Key: ATLAS-2372
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2372
>             Project: Atlas
>          Issue Type: Bug
>          Components:  atlas-core
>    Affects Versions: 1.0.0
>            Reporter: Ashutosh Mestry
>            Assignee: Ashutosh Mestry
>            Priority: Major
>             Fix For: 1.0.0
>
>         Attachments: ATLAS-2372-Export-No-Relationship.patch, 
> ATLAS-2372-Support-Replationships-No-Resource.patch
>
>
> *Background*
> _Relationship_ attributes are supported first class within Atlas. However, 
> the implementation is not supported correctly by the _Export & Import_ 
> ++functionality.
> _Export_ operation works well with _Relationship_ attributes. Each exported 
> entity has correct information present in the _relationshipAttributes_ node.
> _Import_ operation, however, fails during the attribute creation phase of 
> entity creation. This needs to be addressed.
> Export and Import functionality should be functional with entities having 
> _relationshipAttritute_.
> *Short-term Solution*
> During _Export_ process, do not emit the _relationshipAttributes_. _Import_ 
> operation will be functional with low effort.
> Rationale: Existing hive model uses _relationshipAttributes_ but functions 
> well without it. This is compatible with earlier release.
> *Solution*
>  * Process import of entities like before. This will create vertices with 
> correct attributes.
>  * Process relationship attributes for each entity that is part of import 
> process. Edges with correct attributes will get created thus creating 
> _relationshipAttribute._
>  



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

Reply via email to