[CONTROLLER-581] DataChangeListener unable to read created data Created: 24/Jun/14 Updated: 25/Jul/23 Resolved: 25/Jun/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Robert Gallas | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Windows |
||
| External issue ID: | 1240 |
| Description |
|
In application DataChangeListener is registered. Upon sending POST using restconf onDataChanged method is invoked. Following code: Produces output: Subsequent GET on restconf proves POST-ed data are stored into datastore. Since DataCommitHandler has bug registered, this second approach to read created data, is blocker for us. |
| Comments |
| Comment by Tony Tkacik [ 24/Jun/14 ] |
|
You are reading from Operational DAta but you are posting to configuration Operational data CAN NOT be updated via Restconf, that is why you see Marked this as Resolved - Invalid, since Data Change Listeners (using Configuration) methods are verified to be working with Restconf. (https://jenkins.opendaylight.org/integration/job/integration-master-csit-base-of13/ - test restconf puts, components process data as data changes). |
| Comment by Robert Gallas [ 25/Jun/14 ] |
|
Sorry may fault: logger.info("onDataChanged change.getCreatedConfigurationData().entrySet().size()={}", ends up with: As I said in bug creation data are inserted in data store but deserialization fails at data change listener. Hovever there is a difference in output: when logger contains code to read configuration data exception is thorwn: So the steps are: Root cause of exception seems to be: Meaning that even data are succesfully uploaded to datastore 1. in listener I'm unable to read change Code is proprietary so I cannot post code. So only code samples Referencig yang: ... ... In cache there are two ietf-yang-types and both of them contains: ) {5}'; |
| Comment by Robert Gallas [ 25/Jun/14 ] |
|
referencing YANG needes to reference ietf-yang-types by revision as well. After adding revision listener works OK. |