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

unable to parse: invalid number #4433

Closed
snakeye opened this issue Oct 13, 2015 · 2 comments
Closed

unable to parse: invalid number #4433

snakeye opened this issue Oct 13, 2015 · 2 comments

Comments

@snakeye
Copy link

snakeye commented Oct 13, 2015

Hello,

I have met strange issue with the HTTP API:

curl -i -XPOST 'http://localhost:8086/write?db=test' --data-binary 'test value=4.4 1444766780000000000'
HTTP/1.1 204 No Content

curl -i -XPOST 'http://localhost:8086/write?db=test' --data-binary 'test value=4.4e-7 1444766780000000000'
HTTP/1.1 204 No Content

curl -i -XPOST 'http://localhost:8086/write?db=test' --data-binary 'test value=4.4E-7 1444766780000000000'
HTTP/1.1 400 Bad Request
unable to parse 'test value=4.4E-7 1444766780000000000': invalid number

Interesting point that the issue occurs not every time, but only one-two times per minute while influxdb receives ~20 messages per second. From my point of view it should either every float value or no error at all.

@otoolep
Copy link
Contributor

otoolep commented Oct 13, 2015

@jwilder -- is the fix as simple as #4434 ?

@otoolep
Copy link
Contributor

otoolep commented Oct 13, 2015

Thanks for the report @snakeye -- the fix will be in the next nightly build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants