atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Radley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-1734) Import API: Add Support to Update Attributes of Existing Types During Import
Date Sat, 15 Apr 2017 08:03:42 GMT

    [ https://issues.apache.org/jira/browse/ATLAS-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969859#comment-15969859
] 

David Radley commented on ATLAS-1734:
-------------------------------------

[~ashutoshm] i am uncomfortable with an import being able to change the shape of an entity.
Imports should be for creates and updates of entity instances. We would like Atlas to be a
metadata repository for governance - so I suggest we need to control who updates the metadata.
Updating schema- like information should not be done in an import. The import could flag that
there are additional fields associated with entities, so that appropriate type changes could
be made in a controlled way. The import should have controls to determine its behaviour in
these sort of scenarios. I would suggest most companies would want to fail the complete import
if a situation occurred like this - or ignore the unrecognized attributes.    

> Import API: Add Support to Update Attributes of Existing Types During Import
> ----------------------------------------------------------------------------
>
>                 Key: ATLAS-1734
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1734
>             Project: Atlas
>          Issue Type: Improvement
>          Components:  atlas-core
>    Affects Versions: trunk, 0.8-incubating
>            Reporter: Ashutosh Mestry
>            Assignee: Ashutosh Mestry
>              Labels: patch
>             Fix For: trunk
>
>         Attachments: ATLAS-1734-Import-with-additional-attribute-processi.patch
>
>
> *Background*
> Existing version of Import API allows for importing types that are not already present
in the system being imported in. This causes import to fail in the cases where the data being
imported happens to have the additional attribute.
> *Solution*
> During import, existing types are checked to determine if the types being imported have
additional attributes. If additional attributes exist, then the existing type is updated with
the new attributes. The import then proceeds.
> *Impact Assessment*
> - Import API: 
>   -- Type import: Additional capability (mentioned above).
>   -- Entity creation and processing: No impact.
> - Export API: No impact.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message