[YANGTOOLS-916] BindingDOMWriteTransactionAdapter.ensureParentsByMerge() should skip structural containers Created: 03/Feb/16 Updated: 13/Nov/18 |
|
| Status: | Confirmed |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Description |
|
ensureParentsByMerge() emits merge operations for the entire path leading up to the element being introduced. The DataTree manages lifecycle of non-presence containers, which means these are automatically created as needed, hence an explicit merge is not needed. Modify the API and implementation to walk the schema context so that a merge is not triggered for non-presence containers. |
| Comments |
| Comment by Robert Varga [ 13/Nov/18 ] |
|
MD-SAL side of this was resolved by creating a single structure and merging it at root. The structure is controlled by YANGTOOLS, hence this is an improvement so that a new API is created to return an optional/partial structure. |