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

[0.9.3] inserting NaNs causes value to become unqueryable. #4104

Closed
DanielMorsing opened this issue Sep 15, 2015 · 6 comments
Closed

[0.9.3] inserting NaNs causes value to become unqueryable. #4104

DanielMorsing opened this issue Sep 15, 2015 · 6 comments

Comments

@DanielMorsing
Copy link
Contributor

> create database foo
> use foo
Using database foo
> insert cpu value=200
> insert cpu foobar=nan
> select * from cpu
ERR: invalid character 'j' looking for beginning of value
> select value from cpu
name: cpu
---------
time                value
2015-09-15T15:18:10.512161841Z  200

@timraymond
Copy link
Contributor

@DanielMorsing To help with reproducing this issue, could you prefix the title of this issue with the version of Influx that you're encountering this under (e.g. [0.x.x] inserting NaNs...)?

Also helpful information would be the OS that you're using and whether this is a cluster or single node setup.

@malaakso
Copy link

I have the same problem: 0.9.3, Linux, single node.

@beckettsean
Copy link
Contributor

Similar to #3994

@beckettsean beckettsean changed the title inserting NaNs causes value to become unqueryable. [0.9.3] inserting NaNs causes value to become unqueryable. Oct 7, 2015
@luciotorre
Copy link

Fwiw, I have the same problem: 0.9.4, Linux, single node.

@rajeshmurali
Copy link

select * from cpu where value>=0 works,
Case 2:
Now try to insert a value for foobar field
example: insert cpu foobar=123
this query is successful
now try to fetch the values from foobar field by using the query
select * from cpu where foobar>=0

using the query select * from cpu is confusing influxdb or influxdb could not display a field with Not a Number (NaN) value

@jwilder
Copy link
Contributor

jwilder commented Feb 17, 2016

Fixed via 0926b19

@jwilder jwilder closed this as completed Feb 17, 2016
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

7 participants