Need to remove version processing support for patch api
Regarding to the changes in recordId format, we need to remove version processing support for patch api. The old format ordered that recordId should contains at least 3 parts spit by ':' and fourth (optional) part always was version. Now format changed and number of parts split by ':' is not defined.
An example of affected payload:
{
"query": {
"ids": [
"tenant:nam:productionWellHistory:42461358371234.2012-02-01.M-test"
]
},
"ops": [
{
"op": "add",
"path": "/tags",
"value": [
"testtag:testvalue"
]
}
]
}
The id in payload contains 4 parts split by ':'. According to current implementation the id will be considered as id with version, but it is not correct
Edited by Yauheni Lesnikau