[CONTROLLER-522] Promote DataPreconditionFailedException into the public Data Broker API Created: 30/May/14  Updated: 19/Oct/17  Resolved: 18/Jun/14

Status: Resolved
Project: controller
Component/s: mdsal
Affects Version/s: Helium
Fix Version/s: None

Type: Improvement
Reporter: Tony Tkacik Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Windows
Platform: PC

Issue Links:
Blocks
blocks CONTROLLER-523 Milestone: Continuos: Improve error-r... Resolved
blocks CONTROLLER-524 Introduce example which shows read/wr... Resolved

 Description   

Extract DataPreconditionFailedException from Data Store Implementation
and make it part of public data store API as OptimisticLockFailedException
which still carries instance-identifier and message.

Introduce DataVerificationFailedException to Data store, to distinguish from
OptimisticLockFailedException.

Make sure OptimisticLockFailedException is propagated via all future
calls in MD-SAL to the client code.

 Comments   
Comment by Tony Tkacik [ 09/Jun/14 ]

Introduced more explainatory exception OptimisticLockFailedException. Added support to InMemoryDOMData store.

Comment by Tony Tkacik [ 09/Jun/14 ]

https://git.opendaylight.org/gerrit/#/c/7775/

Generated at Wed Feb 07 19:53:14 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.