[
https://issues.apache.org/jira/browse/ATLAS-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15954802#comment-15954802
]
David Radley commented on ATLAS-1713:
-------------------------------------
I agree - the type API should accept the type name or the guid on the REST
endpoint,
Some questions
- The interesting piece is when do you fail a delete of a type.
- I suggest that we should only allow a delete of a type that has no associated
active instances. In this way a single type delete cannot take out many
entities.
- I assume we will soft delete a type - so it is still present in the graph.
- if there are relationships to / from other types - then potentially those
other types are invalidated by the deletion of this type. Another type may
reference or have a non-optional relationship to this type.
I suggest a design doc be created for this item to ensure that the metadata
repository deals with the potential loss of integrity after a type delete.
> V2 API to delete a type requires type definition to given as body
> ------------------------------------------------------------------
>
> Key: ATLAS-1713
> URL: https://issues.apache.org/jira/browse/ATLAS-1713
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
> Affects Versions: 0.9-incubating
> Reporter: Sharmadha Sainath
> Priority: Minor
>
> V2 API
> {code}
> api/atlas/v2/types/typedefs
> {code}
> requires body data when doing a HTTP DELETE request .
> Since type has both name and guid , it could be given as path instead of
> sending the whole type definition as body.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
