atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sarath Subramanian (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ATLAS-2040) Relationship with many-to-many cardinality gives incorrect relationship attribute value when same attribute name and same type specified at both ends
Date Thu, 10 Aug 2017 23:41:00 GMT

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

Sarath Subramanian updated ATLAS-2040:
--------------------------------------
    Description: 
Relationship with many-to-many cardinality gives incorrect relationship attribute value when
same attribute name and same type specified at both ends

When same attribute name and same type is mentioned in both ends of relationship definition.
Creating new relationships fails to retireve the right value.

For e.g.  employee-friends type: same attribute name 'friends' in type 'Employee' specified
at both ends

Add more unit tests to test these cases

  was:
When same attribute name and same type is mentioned in both ends of relationship definition.
Creating new relationships fails to retireve the right value.

For e.g.  employee-friends type: same attribute name 'friends' in type 'Employee' specified
at both ends

Add more unit tests to test these cases


> Relationship with many-to-many cardinality gives incorrect relationship attribute value
when same attribute name and same type specified at both ends
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ATLAS-2040
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2040
>             Project: Atlas
>          Issue Type: Bug
>          Components:  atlas-core
>    Affects Versions: 0.9-incubating
>            Reporter: Sarath Subramanian
>            Assignee: Sarath Subramanian
>
> Relationship with many-to-many cardinality gives incorrect relationship attribute value
when same attribute name and same type specified at both ends
> When same attribute name and same type is mentioned in both ends of relationship definition.
Creating new relationships fails to retireve the right value.
> For e.g.  employee-friends type: same attribute name 'friends' in type 'Employee' specified
at both ends
> Add more unit tests to test these cases



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message