You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Madhan Neethiraj (JIRA)" <ji...@apache.org> on 2018/05/17 00:58:00 UTC
[jira] [Updated] (ATLAS-2610) Import Process: Import from Earlier
Versions Should Set Relationship Defaults
[ https://issues.apache.org/jira/browse/ATLAS-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Madhan Neethiraj updated ATLAS-2610:
------------------------------------
Affects Version/s: (was: trunk)
Fix Version/s: (was: trunk)
1.0.0
Committed to master: http://git-wip-us.apache.org/repos/asf/atlas/commit/30dd2f5b
> Import Process: Import from Earlier Versions Should Set Relationship Defaults
> -----------------------------------------------------------------------------
>
> Key: ATLAS-2610
> URL: https://issues.apache.org/jira/browse/ATLAS-2610
> 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-2610-Relationship-id-during-import.-Tag-propga.patch
>
>
> *Scenario*
> User exports data from v0.8 or before. Importing to v1.0 should set correct defaults for features specific to v1.0.
> *Cases*
> * Relationship GUID should be present on edges. API calls like _findByGuid_ should return _AtlasEntity_ with _relationshipGuid_ set.
> * For classification, _propagateTag_ should be set to _false_ by default.
> * Export-Import-Export verification should set inverse attributes such that they referenced in parent and referring to parent from child.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)