[
https://issues.apache.org/jira/browse/ATLAS-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Kantor updated ATLAS-1040:
--------------------------------
Description: If I pass multiple GUIDs to the DELETE request and some of the
GUIDs do not exist in the repository, then it is throwing an exception without
deleting any thing. It would be more convenient to the application if the
delete method ignores the non-existing GUIDs and delete the other GUIDs instead
of throwing an exception. (was: I am seeing these issues when hard delete is
configured:
1. If I try to delete 2 objects in one DELETE request that has a reference with
lower bound constraint > 0, then the deletion fails indicating that the
deletion violates the lower bound constraint.
2. If I pass multiple GUIDs to the DELETE request and some of the GUIDs do not
exist in the repository, then it is throwing an exception without deleting any
thing. It would be more convenient to the application if the delete method
ignores the non-existing GUIDs and delete the other GUIDs instead of throwing
an exception.)
Summary: Delete of non-existent guids throws exception (was: Delete
issues)
> Delete of non-existent guids throws exception
> ---------------------------------------------
>
> Key: ATLAS-1040
> URL: https://issues.apache.org/jira/browse/ATLAS-1040
> Project: Atlas
> Issue Type: Bug
> Reporter: Prasad S Madugundu
>
> If I pass multiple GUIDs to the DELETE request and some of the GUIDs do not
> exist in the repository, then it is throwing an exception without deleting
> any thing. It would be more convenient to the application if the delete
> method ignores the non-existing GUIDs and delete the other GUIDs instead of
> throwing an exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
