Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InfluxDB 1.8: V2 compatibility write API doesn't support unsigned integers #17781

Open
vlastahajek opened this issue Apr 17, 2020 · 1 comment
Labels
1.x area/compat-v1x v1.x compatibility related work in v2.x

Comments

@vlastahajek
Copy link
Contributor

The line protocol in InfluxDB 2 adds support for unsigned integers (suffix 'u'). V2 compatibility write API in InfluxDB 1.8 doesn't handle this.

Steps to reproduce:
curl -v -XPOST "localhost:8086/api/v2/write?bucket=test" --data-raw "test f=3u"

Expected behavior:
No error

Actual behavior:

< HTTP/1.1 400 Bad Request
< Content-Type: application/json
< Request-Id: a4c703d5-808b-11ea-8007-d66d6d2aa003
< X-Influxdb-Build: OSS
< X-Influxdb-Error: unable to parse 'test f=3u': invalid number
< X-Influxdb-Version: 1.8.0
< X-Request-Id: a4c703d5-808b-11ea-8007-d66d6d2aa003
< Date: Fri, 17 Apr 2020 09:13:04 GMT
< Content-Length: 56
<
{"error":"unable to parse 'test f=3u': invalid number"}
* Connection #0 to host localhost left intact

Environment info:

  • System info: Windows 10 Professional
  • InfluxDB version: InfluxDB v1.8.0 (git: 1.8 781490d)
  • Other relevant environment details: Container runtime, disk info, etc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.x area/compat-v1x v1.x compatibility related work in v2.x
Projects
None yet
Development

No branches or pull requests

4 participants