-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[0.9.2] parser incorrectly accepts NaN as numerical value, but not always #3539
Comments
I have the same issue, we can store NaN value, but then we could do a query that use this value. I can reproduce this issue with 0.9.2 and master (affd0b1). Step to reproduce:
|
I'm incredibly confused now. I can recreate this, but not reliably. Sometimes the unquoted
It should always throw a parser error, or we have to build in support for |
I am using 0.9.2-1 and it seems to me the following case are also failing: |
@beckettsean really no rush, just to plan my tasks, what do you think will it be fixed (in an RC) in the next 3 weeks? |
@kalidasya It's still unscheduled, so the earliest would be in a few weeks. |
The bug can be found in: I hope this helps. |
Probably it is related to: golang/go#3480 (sorry my go knowledge is 0) where they suggest to use custom types for floats: golang/go#3480 (comment) |
Fixes #3539 partially. NaN cannot be queried though and needs to be handled by the query engine differently.
Fixes #3539 partially. NaN cannot be queried though and needs to be handled by the query engine differently.
Please add full support of NaN and +-Inf. |
@zelandoramen1 please make a feature request in a new issue rather than commenting on a closed issue. |
I use the collectd tail plugin, what can report nan when there were no matching data in the tailed file, what somehow causes corruption in the influxdb db. If it happens a query like:
select * from /.*/
orselect * from tail_value
will die with:ERR: invalid character 'j' looking for beginning of value
the easiest way to reproduce is to add the following config to collectd:
most likely after collectd runs, you will see nan reported, you can always echo some stuff to it like:
echo "something blah" >> /tmp/reproduce_it.log
The text was updated successfully, but these errors were encountered: