[CONTROLLER-193] Restconf must support reading operational data from a higher level container Created: 06/Mar/14 Updated: 25/Jul/23 Resolved: 08/Apr/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Ashwin Pankaj | Assignee: | Tony Tkacik |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Linux |
||
| Issue Links: |
|
||||||||
| External issue ID: | 485 | ||||||||
| Description |
|
If I set an operational attribute a/b/c - to retrieve that value I need to query using that path only. Restconf should support querying from higher containers like read a/b - should give all the operational data within b - including c. |
| Comments |
| Comment by Tony Tkacik [ 10/Mar/14 ] |
|
Could you please provide steps to reproduce and if possible your logs - This is working fine for openflow end-to-end use case - where you write flows and read its parent (table). |
| Comment by Tony Tkacik [ 08/Apr/14 ] |
|
Fixed by using new Data store (see configuration/initial/01-md-sal.xml) for switching to new data store. |