Skip to content

fix issue with records batch api as it drops valid record after conversion

Neelesh Thakur requested to merge fix-batch-api-meta-geo into master

Record batch API incorrectly responding with notFound error for certain records combination, e.g.

curl --location 'http://host/api/storage/v2/query/records:batch' \
--header 'data-partition-id: opendes' \
--header 'frame-of-reference: units=SI;crs=wgs84;elevation=msl;azimuth=true north;dates=utc;' \
--header 'Authorization: Bearer ' \
--header 'Content-Type: application/json' \
--data '{
    "records": [
        "opendes:master-data--Wellbore:ce85d8c5a4e75e2881e0f19a047e70b69191ea86dd13a71b9928cfa273f40e55",
        "opendes:master-data--Wellbore:387fe57d5deac0533a78c7cf26f1d01324f442d506262913f17dad885c4a4b71"
    ]
}

Where opendes:master-data--Wellbore:ce85d8c5a4e75e2881e0f19a047e70b69191ea86dd13a71b9928cfa273f40e55 has AsIngestedCoordinates as well valid meta block & opendes:master-data--Wellbore:387fe57d5deac0533a78c7cf26f1d01324f442d506262913f17dad885c4a4b71 has AsIngestedCoordinates but no or empty meta block, then for such cases batch API responds with notFound for opendes:master-data--Wellbore:387fe57d5deac0533a78c7cf26f1d01324f442d506262913f17dad885c4a4b71 record-id, even though there is nothing wrong with record or FoR conversion on record data.

Merge request reports