One entry of a batch the index refused, reported by a request sent with ?onError=skip. The entry is named by position for a caller walking the list it sent, and also by line for a caller pointing at a newline-delimited file.
Example
{
"position": 3,
"line": 4,
"errors": [
{
"code": "document:field_unknown",
"message": "Field `nonexistent` does not exist in index",
"path": "documents[3].nonexistent",
"arguments": {
"position": "3",
"processed": "3",
"name": "nonexistent"
}
}
]
}
Properties
positioninteger
Which entry of the batch this was, counted from zero. Matches the index in the path of each error.
Format
int32
Example
3
lineinteger
The line of the request body the entry starts on, counted from one. Present only for a newline-delimited body; a body that carries the entries in a documents array omits it.
"message": "Field `id` is marked as a primary key and multiple, primary keys can not have multiple values",
"path": "id"
}
4 properties
codestring
The error code identifying this specific problem.
Example
"index:field:primary_key:multiple_unsupported"
messagestring
Human-readable description of this problem.
Example
"Field `id` is marked as a primary key and multiple, primary keys can not have multiple values"
pathstring
Location of the offending value in the request, such as fields.title or documents[1].nonexistent. Names join with ., one element of a list reads [n] counted from zero, and a key of a free-form map such as metadata goes in brackets and double quotes when it holds a dot or a bracket, as metadata["build.sha"]. A field inside an object field carries its own dotted path, so a path here reaches a field the same way a query does. Omitted when the problem applies to the request as a whole. See API conventions.
Example
"id"
argumentsmap of string
The values the message was rendered with, so a client can render a message of its own from the code.
1 property
<key>string
Endpoints
Endpoints where the request or responses uses this type.