POST /query/records:batch with normalization stops converting after 1 conversion failure
An attribute was defined as a number in the schema:
"depthA": {
"title": "depthA",
"type": "number"
}
The meta specified is to convert the values in depthA from ft to meter.
"meta": [
{
"kind": "Unit",
"name": "ft",
"persistableReference": "{\"scaleOffset\":{\"scale\":0.3048,\"offset\":0.0},\"symbol\":\"ft\",\"baseMeasurement\":{\"ancestry\":\"Length\",\"type\":\"UM\"},\"type\":\"USO\"}",
"propertyNames": [
"depthA",
"depthB"
],
The record was ingested/created with an empty string assigned to depthA.
"data": {
"depthA": "",
"depthB": 123,
"depthC": 456
},
Upon record creation, fetch API was called to normalize the record before indexing. The conversion failed to convert depthA. An error was logged. Fetch API returned a 200, but with a conversion error.
After this error, the API skipped conversion for other attributes.
Indexer saw this error and returned a 400 status. Trace index trace returns:
"statusCode": 400,
"trace": [
"Unit conversion: illegal value for property depthA"
]
Action: API should continue to convert all specified attributes, and log the conversion errors for those that failed.