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] Less than or equal to inequality is not inclusive for time in where clause #4193

Closed
bal2ag opened this issue Sep 22, 2015 · 1 comment · Fixed by #4822
Closed

[0.9.3] Less than or equal to inequality is not inclusive for time in where clause #4193

bal2ag opened this issue Sep 22, 2015 · 1 comment · Fixed by #4822

Comments

@bal2ag
Copy link

bal2ag commented Sep 22, 2015

OS: OS X 10.10.4 (although I have seen the same issue on other OSes)
InfluxDB version: 0.9.3
Install: Pre-built package
Test case: Should be able to repro on any database, just format the query as below using <= for time upper bound.

I have the following data in my InfluxDB database (among other data):

...
2015-09-09T07:56:00Z        testapp1    testbeacon1 herp    testent1
2015-09-09T07:56:47Z        testapp1    testbeacon1 herp    testent1
2015-09-09T08:22:15Z        testapp1    testbeacon1 herp    testent1
...

When I try to query using an inclusive upper and lower bound on time, only the lower bound is actually inclusive - the upper bound is exclusive.

> select * from ping where time >= '2015-09-09T07:56:00Z' and time <= '2015-09-09T08:22:15Z'
name: ping
----------
time            application_id  beacon_id   derp    entity_id
2015-09-09T07:56:00Z    testapp1    testbeacon1 herp    testent1
2015-09-09T07:56:47Z    testapp1    testbeacon1 herp    testent1

Can anyone shed some light on what might be happening? Is the <= inequality not supported? Is there some sort of clock skew issue?

Thanks very much.

@rkuchan
Copy link
Contributor

rkuchan commented Sep 22, 2015

Thanks, @bal2ag! I was able to repro. This is a bug.

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

Successfully merging a pull request may close this issue.

4 participants