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

DELETE neglects the most recent value. #8315

Closed
inselbuch opened this issue Apr 21, 2017 · 1 comment
Closed

DELETE neglects the most recent value. #8315

inselbuch opened this issue Apr 21, 2017 · 1 comment
Assignees
Milestone

Comments

@inselbuch
Copy link

inselbuch commented Apr 21, 2017

Bug report

System info: [Include InfluxDB version, operating system name, and other relevant details]

InfluxDB shell version: 1.2.0
Connected to http://localhost:8086 version 1.2.0
Linux ubuntu 4.9.7-x86_64-linode80 #2 SMP Thu Feb 2 15:43:55 EST 2017 x86_64 x86_64 x86_64 GNU/Linux

Steps to reproduce:

  1. select a range of time series values from a measurement

select * from measurement where mac = 'b827eb30bf6d'

2017-02-28T20:00:00Z 233.183333334 b827eb30bf6d
2017-02-28T21:00:00Z 233.183333334 b827eb30bf6d
2017-02-28T22:00:00Z 233.183333334 b827eb30bf6d
2017-02-28T23:00:00Z 233.183333334 b827eb30bf6d
2017-03-01T00:00:00Z 233.183333334 b827eb30bf6d
2017-03-01T01:00:00Z 233.183333334 b827eb30bf6d
2017-03-01T02:00:00Z 233.183333334 b827eb30bf6d
2017-03-01T03:00:00Z 233.183333334 b827eb30bf6d
2017-03-01T04:00:00Z 233.183333334 b827eb30bf6d
2017-03-01T05:00:00Z 233.183333334 b827eb30bf6d
2017-03-01T06:00:00Z 233.183333334 b827eb30bf6d
2017-03-01T07:00:00Z 233.183333334 b827eb30bf6d
many more values
2017-04-21T10:00:00Z 233.183333334 b827eb30bf6d
2017-04-21T11:00:00Z 233.183333334 b827eb30bf6d
2017-04-21T12:00:00Z 233.183333334 b827eb30bf6d
2017-04-21T13:00:00Z 233.183333334 b827eb30bf6d
2017-04-21T14:00:00Z 233.183333334 b827eb30bf6d

  1. delete all values after a specified time

delete from measurement where mac = 'b827eb30bf6d' and time > '2017-02-28T20:00:00Z'

  1. examine the remaining values, notice the value that should not remain (emphasis added)

2017-02-28T09:00:00Z 229.416666667 b827eb30bf6d
2017-02-28T10:00:00Z 229.416666667 b827eb30bf6d
2017-02-28T11:00:00Z 229.416666667 b827eb30bf6d
2017-02-28T12:00:00Z 229.416666667 b827eb30bf6d
2017-02-28T13:00:00Z 229.416666667 b827eb30bf6d
2017-02-28T14:00:00Z 229.416666667 b827eb30bf6d
2017-02-28T15:00:00Z 230.333333334 b827eb30bf6d
2017-02-28T16:00:00Z 231.250000001 b827eb30bf6d
2017-02-28T17:00:00Z 232.066666668 b827eb30bf6d
2017-02-28T18:00:00Z 232.366666668 b827eb30bf6d
2017-02-28T19:00:00Z 232.600000001 b827eb30bf6d
2017-02-28T20:00:00Z 233.183333334 b827eb30bf6d
2017-04-21T14:00:00Z 233.183333334 b827eb30bf6d

Expected behavior:

All values meeting the criteria should have been deleted.

Actual behavior: [What actually happened]

One value remains that shouldn't.

Additional info: [Include gist of relevant config, logs, etc.]

Please note, the quickest way to fix a bug is to open a Pull Request.

@jwilder
Copy link
Contributor

jwilder commented Apr 21, 2017

You may be seeing this: #7798 (comment)

@rbetts rbetts added this to the 1.3.0 milestone Apr 26, 2017
@ghost ghost added the review label Apr 27, 2017
@ghost ghost removed the review label Apr 28, 2017
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

4 participants