+1 We have faced similar issues in Genius project as well. Thanks, Faseela
From: controller-dev-boun...@lists.opendaylight.org [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Sela, Guy Sent: Thursday, January 19, 2017 10:30 PM To: Robert Varga <n...@hq.sk>; controller-dev@lists.opendaylight.org; mdsal-...@lists.opendaylight.org; Tom Pantelis <tompante...@gmail.com> Subject: [controller-dev] Deleting a node from MD-SAL that doesn't exist / already deleted When submitting a delete transaction on a node that doesn't exist, MD-SAL's behavior is to throw ModifiedNodeNotExists Exception. There are many usecases where there is a "cleanup" code that tries to delete some state even though it is not 100% there, just for the sake of cleanup. I saw it in netvirt where delete flow operations get exceptions because the flow is not there. My question is more of a design issue, isn't an exception in this case is "too brutal"? The API could succeed with some kind of a different result code? Alternatively, the API could let me pass an argument to the delete operation, if I want an exception in case Node doesn't exist or not. Thanks, Guy Sela
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
