Pierre Padovani commented on ATLAS-1764:

My use case:

Consider a composite metadata entity that is made up of many (50-70+) Atlas 
entities. This composite entity is pulled in order to drive a portion of a data 
pipeline. The composite might contain things like:
* tables
* columns
* config
* target system information

Individually, the small Atlas metadata entities are useless to the data 
pipeline, only if the runtime engine has all of the metadata required will it 
be able to function.   Currently composing and decomposing an entity such as 
this requires specialized code that understands how to traverse and retrieve 
all of the pieces. Implementing a form of entity collection would allow for the 
creation of these types of composed metadata sets that could be retrieved etc. 
far easier.

> Design and implement Atlas Collections
> --------------------------------------
>                 Key: ATLAS-1764
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1764
>             Project: Atlas
>          Issue Type: New Feature
>          Components:  atlas-core
>    Affects Versions: 0.9-incubating
>            Reporter: Sarath Subramanian
>            Assignee: Sarath Subramanian
>              Labels: features
> Design and implement Atlas Collections - A first class element in Atlas to 
> group related entities together and perform operations on these collections - 
> associate tags, add/remove entities...
> Operations:
> ---------------
>     a. Create collection(s) with attributes, constraints
>     b. Update existing collection(s)
>     c. Delete collection(s) - soft delete, hard delete
>     d. Retrieve collections by id, name
>     e. Add entity(s) to collection(s)
>     f. Remove entity(s) from collection(s)
>     g. Associate classification(s) to collection(s)
>     h. Disassociate classification(s) from collection(s)

This message was sent by Atlassian JIRA

Reply via email to