Expected BEGIN_OBJECT but was NUMBER at line 22 column 63
But the input is too short, it does not contain line 22.
Can you please provide us with example of successful PUT/POST and unsuccessful PATCH with the same values/data?
Example using the o-ran-delay-management module of the O-RAN simulator:
PUT
/rests/data/network-topology:network-topology/topology=topology-netconf/node=nts-ng-sim/yang-ext:mount/o-ran-delay-management:delay-management
{
"o-ran-delay-management:delay-management": {
"adaptive-delay-configuration": {
"bandwidth-scs-delay-state": [
{
"bandwidth": 3000,
"subcarrier-spacing": 20,
"o-du-delay-profile": {
"tx-max": 100,
"ta4-max": 100,
"t1a-max-up": 100,
"rx-max": 100,
"t1a-max-cp-dl": 100
}
}
]
}
}
}
Corresponding PATCH
/restconf/config/network-topology:network-topology/topology/topology-netconf/node/nts-ng-sim/yang-ext:mount/
{
"ietf-restconf:yang-patch": {
"patch-id": "patch-1",
"edit": [
{
"edit-id": "edit1",
"operation": "merge",
"target": "/o-ran-delay-management:delay-management/o-ran-delay-management:adaptive-delay-configuration",
"value": {
"adaptive-delay-configuration": {
"bandwidth-scs-delay-state": [
{
"bandwidth": 3000,
"subcarrier-spacing": 20,
"o-du-delay-profile": {
"tx-max": 100,
"ta4-max": 100,
"t1a-max-up": 100,
"rx-max": 100,
"t1a-max-cp-dl": 200
}
}
]
}
}
}
]
}
}
error message:
{
"errors": {
"error": [
{
"error-type": "protocol",
"error-tag": "malformed-message",
"error-message": "Error parsing json input: Expected BEGIN_OBJECT but was NUMBER at line 13 column 50 path $.ietf-restconf:yang-patch.edit[0].value.adaptive-delay-configuration.bandwidth-scs-delay-state[0].bandwidth",
"error-info": "Expected BEGIN_OBJECT but was NUMBER at line 13 column 50 path $.ietf-restconf:yang-patch.edit[0].value.adaptive-delay-configuration.bandwidth-scs-delay-state[0].bandwidth"
}
]
}
}
If all numerical values are submitted as strings (e.g. "bandwidth: "3000"), the PATCH request is executed.
Thanks!
achrestin You are using tow different versions of RESTCONF.
With rests/data you are using RFC8040 version what is better for you 
With restconf/config you are using bierman-02 version - which is deprecated and in recent ODL version removed.
Please use /rests/data/network-topology:network-topology/topology=topology-netconf/node=nts-ng-sim/yang-ext:mount as URI in your PATCH request and everything will be ok.
Thanks for the clarification!
Just a small addition:
It seems that for the bierman-02 version, the Content-Type header field must be set to "application/yang.patch+json", while it must be "application/yang-patch+json" for the RFC8040 version.
Yes, RFC8040 follows RFC8072, bierman02 follows draft-ietf-netconf-patch-XX, where XX is a number I do not remember.
The evolution of media types is evident in the draft changelog .
Please use the same version of RESTCONF when you expect the same results.
It looks there is no bug.