[
https://issues.apache.org/jira/browse/ATLAS-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994407#comment-15994407
]
David Radley commented on ATLAS-1764:
-------------------------------------
Hi [[email protected]],
This is a great Jira. Some up front thoughts:
- I assume a collection could have a type . For example, we could have a
collection of Hive tables.
- I am not sure what constraints and attributes you are envisaging are useful
for a collection. Maybe whether the collection is ordered might be a useful
constraint or maximum size.
- I am not sure what a classification on a collection means. It would be good
to have a use case for this.
- Is a collection going to be defined using a CollectionDef or type in
EntityDef . If suggest it be an EntityDef type if that is possible.
- Can we have an attribute pointing to a collection?
- I wonder if we can have collections in collections and allow set based
operations like unions.
> 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)