[NETCONF-268] Make WriteRunningTx conform to DataBroker API Created: 06/Sep/16 Updated: 15/Mar/19 Resolved: 04/Oct/16 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Jakub Morvay | Assignee: | Andrej Mak |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 6635 |
| Description |
|
Transaction implementation (WriteRunningTx) for netconf devices, that support only writable-running capability does not conform to DataBroker API and differs in behavior from other two implementations (WriteCandidateRunningTx and WriteCandidateTx). Namely, write operations are instantly reflected on device. Submit and cancel does virtually nothing. Write operations should be local to the transaction and not processed until submit is called. |
| Comments |
| Comment by Andrej Mak [ 19/Sep/16 ] |