[CONTROLLER-160] When NodeConnector is augmented with statistics DataChange change sets are not properly populated Created: 15/Feb/14 Updated: 25/Jul/23 Resolved: 15/Jul/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Moiz Raja | Assignee: | Moiz Raja |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| Description |
|
When NodeConnector is augmented with statistics, the updated change set contains only the augmentation data not the complete NodeConnector data. Expectation: The complete NodeConnector data should be in the updated set so that if we need to distinguish what changed in the NodeConnector it would be possible to do it. Note: While this bug refers to a NodeConnector this issue is application to any data node change. |
| Comments |
| Comment by Tony Tkacik [ 27/Feb/14 ] |
|
Original design assumption was that it will only contains change ser (in that case augmentation). Unfortunatelly that was unclear in the API contract. Marking this as enhacement, which will be incorporated in near time. |
| Comment by Tony Tkacik [ 19/Jun/14 ] |
|
Is still this bug observed with new data store? |
| Comment by Tony Tkacik [ 15/Jul/14 ] |
|
Not reproducible on master, |