ISSUE-28: transaction/rollback when deleting resources from a LDPC

bertails

transaction/rollback when deleting resources from a LDPC

State:
CLOSED
Product:
Linked Data Platform Spec
Raised by:
Alexandre Bertails
Opened on:
2012-11-02
Description:
The DELETE operations defined in 5.6.* have impacts on one or more resources. The specification does not define the behavior for when deleting one of the resources had failed during the transaction.

The spec must define a notion of transaction with a rollback mechanism in case of error. The general case would be: if something fails when deleting/modifying one the impacted resources, then the server returns an error (with a message explaining the error) and no resource is deleted. This should be captured in at least 5.6.1 and 5.6.2.

I'm not sure about the following case though: the "child" LDPR for a given LDPC may not be on the same server. It may be a bad idea to return an error if a distant resource couldn't be deleted.


CLOSED:
<RRSAgent> See http://www.w3.org/2013/03/13-ldp-irc#T15-08-40
Related Actions Items:
No related actions
Related emails:
  1. Re: Do we need transaction support in LDP? (from lehors@us.ibm.com on 2013-05-09)
  2. Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (from ashok.malhotra@oracle.com on 2013-04-05)
  3. Re: ldp-ISSUE-28 (bertails): transaction/rollback when deleting resources from a LDPC [Linked Data Platform core] (from bertails@w3.org on 2012-11-05)
  4. Re: ldp-ISSUE-28 (bertails): transaction/rollback when deleting resources from a LDPC [Linked Data Platform core] (from richard@cyganiak.de on 2012-11-05)
  5. Re: ldp-ISSUE-28 (bertails): transaction/rollback when deleting resources from a LDPC [Linked Data Platform core] (from bertails@w3.org on 2012-11-05)
  6. Re: ldp-ISSUE-28 (bertails): transaction/rollback when deleting resources from a LDPC [Linked Data Platform core] (from richard@cyganiak.de on 2012-11-05)
  7. ldp-ISSUE-28 (bertails): transaction/rollback when deleting resources from a LDPC [Linked Data Platform core] (from sysbot+tracker@w3.org on 2012-11-02)

Related notes:

Resolution: A server MUST NOT delete a container unless all members have been successfully deleted. A server MUST NOT respond 200 unless deleting the container and all members succeeded.

See http://www.w3.org/2012/ldp/meeting/2013-03-13#resolution_1

Arnaud Le Hors, 14 Mar 2013, 04:09:57

No changes made by editor's due to resolution of ISSUE-59 which relaxed the delete semantics to be just like http delete...server does not need to delete contents and therefore not have to report or rollback on errors

Steve Speicher, 17 May 2013, 17:13:37

Display change log ATOM feed


Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 28.html,v 1.1 2015/08/17 04:43:08 denis Exp $