atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Mestry (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ATLAS-1825) Import API: Ability to Apply Transforms to Attributes During Import
Date Tue, 30 May 2017 17:51:04 GMT

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

Ashutosh Mestry updated ATLAS-1825:
-----------------------------------
    Attachment:     (was: ATLAS-1825-Import-transform.2.patch)

> Import API: Ability to Apply Transforms to Attributes During Import
> -------------------------------------------------------------------
>
>                 Key: ATLAS-1825
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1825
>             Project: Atlas
>          Issue Type: Improvement
>          Components:  atlas-core
>    Affects Versions: trunk
>            Reporter: Ashutosh Mestry
>            Assignee: Ashutosh Mestry
>             Fix For: trunk
>
>         Attachments: ATLAS-1825-Import-transform.4.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> h3. Scenarios
> *Case 1*
> In a situation where, data exported from a cluster is imported to a different cluster,
it is necessary to make changes to attributes of entities such that their values represent
their environment
> Example: Entities exported from cluster called _'cl1'_ will have _@cl1_ in their qualifiedName
attribute. When these entities are imported to a cluster called _'cl2'_ the qualifiedName
attribute should read _@cl2_ to correctly reflect their new environment.
> *Case 2*
> Exported data contains an attribute that has value that does not conform to the conventions
followed within the cluster. This can be corrected by exporting the data and reimporting it
with an applied transform.
> Example: Entities were created with an attribute value as upper case, this needs to be
lower case to conform to a convention.
> h3. Solution
> As part of Import API, it will help to be able to specify in a generic manner the transforms
that could be applied to an entity type.
> The implementation should be extensible so that new transforms could be added in future.



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

Mime
View raw message