[YANGTOOLS-327] StreamWriter APIs loses information about leaf-set ordering Created: 24/Sep/14 Updated: 10/Apr/22 Resolved: 12/Jan/16 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Tony Tkacik | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 2062 | ||||||||
| Description |
|
leaf-list noderefs { BindingStreamEventWriter and NormalizedNodeStreamWriter APIs looses information This caused reordering of leaf-list entries. Ordered-by statement works for list items. User ordered leaf-list are supported in Data Store and other pieces of infrastructure. |
| Comments |
| Comment by Jan Hajnar [ 11/Nov/14 ] |
|
fix: clustering modification that is dependent on NormalizedNodeStreamWriter: |
| Comment by Jan Hajnar [ 11/Aug/15 ] |
|
Hi, Since in Lithium we preserve leaf-list ordering and patch for this issue didn't get merged into Helium SR4, final status for this issue is fixed in Lithium and won't fix in Helium. Jan. |
| Comment by Robert Varga [ 07/Jan/16 ] |
|
The fix was not actually delivered and the problem was reported again against Li SR3, affects Be, too. |
| Comment by Robert Varga [ 08/Jan/16 ] |
|
Li: Be: |