Storage returns inconsistent and wrong responses if nested attribute filters which do not exist are specified
Using /api/storage/v2/records/{id} optional attribute filter:
Example, given this data:
"data": {
"relationships": {
"well": {
"id": "slb-osdu-tryme:well",
"name": "Card Creek 2"
},
"relatedItems": {
"ids": [
"Log1",
"Marker1"
],
"names": [
"Log Name1",
"Marker Name1"
]
}
}
A few observances when filtering with string:
data.something returns 200 data.relationships.something returns 200 data.relationships.well.something returns 200 data.relationships.well.number returns 500 at first. Then after a few tries, it returns 200. data.relationships.something returns 200 data.relationships.relatedItem.something returns 500 (no s on relatedItems) data.relationships.relatedItems.something returns 500 at first, then 200 after that.
Expected return code should be 400.