...
| # | Issues | Notes | Decision |
|---|---|---|---|
| 1 | do we need separate operation for list or can we support all variations using same solution without interface changes | Toine Siebelink Prefer single solution that address all scenarios (multiple containers or list entries) correctly without interface changes. | |
| 2 | Should all patch operations be part of singel single transaction | for now treat individual | |
| 3 | what to do with failures |
| |
| 4 | What if a new data node(list item/container)is sent in the patch? |
| Lukasz Rajewskibrought up the point where if a new item is sent in the update request then what will be the expected behavior of CPS. |
| 5 | How will we match the data nodes? | For example there are 10 data nodes and update is done on data nodes at position 1,5 and 9. How will the data nodes be matched? Because the payload will have only the 1st 5th and 9th data node with updated values | Arne Chrestin raised the following concern. Need to figure out how the matching of data nodes will take place in this scenario |
Initial findings
When trying to perform Patch operation on a list data node, wherein multiple list items are updated in one request. It is seen that only the top most item in the list gets updated where as the remaining list items remain as it is.
...
- Iterate over top-level element in patch.
- match each top element element to target data
- execute each patch
- Transactional ?!
- test & demo for each scenario
- top level containers
- top level list elements
- list elements under same continaercontainer