[
https://issues.apache.org/jira/browse/ATLAS-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994843#comment-15994843
]
Nigel Jones commented on ATLAS-1764:
------------------------------------
I'd be interested in what you see the use cases as.
I can see how a heterogeneous collection could be a convenient way of doing set
operations - retrieval, deletion, bulk updates. When it comes to any kind of
association, such as classification, is that then assigned to the actual
collection object - which implies it really is first class? Or is it just doing
a set operation on list of entity ids?
> 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
(v6.3.15#6346)
