-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[v0.9-rc30&31][prebuilt] No results when testing against a boolean field in WHERE clause #2635
Comments
@renan- I don't believe boolean is a supported datatype. Most likely you are either storing the integer Can you provide a sample of your writes? What are the results of |
Turns out boolean is supported in the datastore but it looks like none of the operators handle them properly. So, although the underlying data has the right value for the boolean, you can't match those values with To reproduce, post this point:
We can see that the
|
@renan- thanks for the bug report, we've got a repro case now so it should get fixed fairly quickly. |
fix #2635: Fix query against bool field in WHERE
Thank you for the quick reply ! |
Hi,
I'm quite a newcomer to InfluxDB, I mean I've been playing around with it and Grafana for the past couple of days. I started with v0.8.8 on Ubuntu 14.04 (64-bits) which worked just fine, but then I switched to 0.9-rc30 and encountered this strange behavior:
I have a serie holding data on each request made to the server, and it has a field called "exception". It's a boolean indicating if there was an error during the request (typically http 500's). I need this information so I tried to retrieve all the requests that resulted into an error (25% in my testing data) :
But this query (through the web interface) returns field names, but no values (it's the same with false or <> operator).
Whereas this one works just fine :
(returns a dozen of points for my data)
I tried to use a string tag set to 'T' or 'F' and it worked but that's just not the right way of doing it...
I first noticed this behavior on 0.9-rc30 but it seems to be just the same in rc31.
Thanks for your time,
Renan
The text was updated successfully, but these errors were encountered: