You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@atlas.apache.org by "Prasad S Madugundu (JIRA)" <ji...@apache.org> on 2016/07/21 11:19:20 UTC

[jira] [Created] (ATLAS-1040) Delete issues

Prasad  S Madugundu created ATLAS-1040:
------------------------------------------

             Summary: Delete issues
                 Key: ATLAS-1040
                 URL: https://issues.apache.org/jira/browse/ATLAS-1040
             Project: Atlas
          Issue Type: Improvement
            Reporter: Prasad  S Madugundu


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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)