Daemon returns different formats of error message

[Nick-S-2018]

In some cases, daemon can return different formats of error message for the same operation. The returned format depends on a specific error. E.g., here are two responses for the insert request when daemon is used without Buddy:

curl -X POST localhost:9308/sql?mode=raw -d "query=create table test(f text)"
[{"total":0,"error":"","warning":""}]

curl -sX POST http://localhost:9308/insert  -d '{
  "index":"test",
  "id":1,
  "doc":
  {
    "f" : "a"               
  }
}'
{"_index":"test","_id":1,"created":true,"result":"created","status":201}

curl -sX POST http://localhost:9408/insert  -d '{
  "index":"test",
  "id":1,
  "doc":
  {
    "f" : "a"
  }
}'
{"error":{"type":"duplicate id '1'","index":"test"},"status":409}

curl -sX POST http://localhost:9408/insert  -d '{
  "index":"test",
  "id":-1,
  "doc":
  {
    "f" : "a"
  }
}'
{"error":"Negative document ids are not allowed"}

This can lead to problems with our OpenAPI-generated clients, so we should think of unifying those response formats in some way.

[tomatolog]

/sql endpoint returns the exact reply from buddy wrapped into array

we could change that but when multi queries will not work - maybe it needs another buddy replication protocol improvement

[Nick-S-2018]

I think, it would be enough to implement a unified format just for insert/replace/update/delete endpoints. As the problem with OpenAPI clients seems to affect only error responses from those ones. So we won't need to change the current handling of /sql or other endpoints.
Can we add the type, index and status properties to all the error responses where they're absent now?
E.g.:
{"error":"Negative document ids are not allowed"}
would become:
{"error":{"type":"Negative document ids are not allowed", "index":"test"},"status":"some appropriate status code"}
and so on.

[sanikolaev]

As discussed, please provide more info on how the queries are executed (i.e. what Buddy receives/returns)

[sanikolaev]

It looks like it was assigned to Nick by mistake. Reassigning to @tomatolog to estimate.

[sanikolaev]

This issue blocks manticoresoftware/openapi#16

[tomatolog]

fixed at the https://github.com/manticoresoftware/manticoresearch/tree/doc_post_error branch as I changed error format for insert/replace/update/delete HTTP JSON endpoints to be the same as it is in the compatibility mode, ie has error object with the string properties type and reason and status. The type has the predefined type of the error from the list searchdhttp.cpp#L3418 and the reason is the error message.

{
    "error": {
        "type": "parse_exception",
        "reason": "Content-Type must be application/x-ndjson"
    },
    "status": 400
}

That is different from the initial description at #1808 (comment) however that reduces the error formats for HTTP JSON endpoints.

I push the change in the branch as think that could break the different APIs and this change should be merged into master along with the API change.

[tomatolog]

I'd also add different types of error.type as now all insert/replace/update/delete returns only parse_exception and runtime error action_request_validation_exception but that is a large change and I'd add it after the branch got merged into master