[YANGTOOLS-686] [Yang 1.1] Allow non-unique values in non-configuration leaf-lists Created: 07/Oct/16 Updated: 18/Jan/24 |
|
| Status: | Confirmed |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | 2.0.0, 1.2.0, 1.1.0 |
| Fix Version/s: | None |
| Type: | New Feature | ||
| Reporter: | Peter Kajsa | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| Comments |
| Comment by Peter Kajsa [ 02/Feb/17 ] |
|
This is not yang parser related issue, hence moved to nitrogen. |
| Comment by Robert Varga [ 28/Oct/17 ] |
|
This change needs further analysis, related to yang-data-api/impl and its relationship to yang-model-api. Furthermore it has implications on replace operations – we really will need a new data structure to support insert/move operations as well as uniqueness constraints. Allowing non-unique values in operational data store means applications cannot perform a straight oper -> config data translation, as they could end up writing non-unique values into config, triggering surprising run-time errors. This change will need to be re-evaluated in 3.0.0 timeframe, but I am leaning towards closing this as won't fix. |