You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Jeffrey Hagelberg (JIRA)" <ji...@apache.org> on 2017/02/06 18:42:41 UTC
[jira] [Updated] (ATLAS-1528) reverseReferenceName lost during type
conversion
[ https://issues.apache.org/jira/browse/ATLAS-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeffrey Hagelberg updated ATLAS-1528:
-------------------------------------
Description:
When a type is converted from the V1 format to V2 and then back to V1, the reverse reference name from the original type is lost. See RestUtils.testBidirectonalCompositeMappingConsistent and RestUtils.testBidirectonalCompositeMappingNonCompositeConsistent for details. These tests are being added in https://reviews.apache.org/r/56126. They are currently disabled due to this issue.
Note - I just rebased my changes, and it looks like a lot of the logic that was causing problems before has been replaced. I'll update once I've figured out whether or not this is still an issue,
was:When a type is converted from the V1 format to V2 and then back to V1, the reverse reference name from the original type is lost. See RestUtils.testBidirectonalCompositeMappingConsistent and RestUtils.testBidirectonalCompositeMappingNonCompositeConsistent for details. These tests are being added in https://reviews.apache.org/r/56126. They are currently disabled due to this issue.
> reverseReferenceName lost during type conversion
> ------------------------------------------------
>
> Key: ATLAS-1528
> URL: https://issues.apache.org/jira/browse/ATLAS-1528
> Project: Atlas
> Issue Type: Bug
> Reporter: Jeffrey Hagelberg
>
> When a type is converted from the V1 format to V2 and then back to V1, the reverse reference name from the original type is lost. See RestUtils.testBidirectonalCompositeMappingConsistent and RestUtils.testBidirectonalCompositeMappingNonCompositeConsistent for details. These tests are being added in https://reviews.apache.org/r/56126. They are currently disabled due to this issue.
> Note - I just rebased my changes, and it looks like a lot of the logic that was causing problems before has been replaced. I'll update once I've figured out whether or not this is still an issue,
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)