different error-message structure in influxdb 1.8.x and 2.0.x when using InfluxQL

[gabor]

Steps to reproduce:

1. using influxdb 1.8.4, execute an invalid query using a POST request at /query, for example the query "SOMETHING"
2. the returned JSON will be like this:

{
    "error": "error parsing query: found SOMETHING, expected SELECT, DELETE, SHOW, CREATE, DROP, EXPLAIN, GRANT, REVOKE, ALTER, SET,
KILL at line 1, char 1"
}

3. do the same with influxdb 2.0.4 (where the influxql-compatibility-things have been set up)
4. the returned JSON will be like this:

{
    "code": "invalid",
    "message": "failed to parse query: found SOMETHING, expected SELECT, DELETE, SHOW, CREATE, DROP, EXPLAIN, GRANT, REVOKE, ALTER,
SET, KILL at line 1, char 1"
}

5. the error-message structure is different between influxdb1 and influxdb2

Expected behavior:
Influx1 and Influx2 use the same error-message structure when queried in influxql-mode

Actual behavior:
Influx1 and Influx2 have different error-message structures when queried in influxql-mode

Environment info:

• System info: docker
• InfluxDB version: 1.8.4 and 2.0.4 in docker

Config:
default config used.

[alaendle]

The same is unfortunately true for the /write endpoint. E.g. v2 returns {"code":"unprocessable entity","message":"failure writing points to database: partial write: points beyond retention policy dropped=1"} while v1 has an error element.