-
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
Error: fields not supported in WHERE clause during deletion #8678
Comments
Can you double check your repro steps? I followed your steps with |
Hi @e-dard, I tried again with the same result. I also tried to turn off new engine |
@nargiza-sarkulova that you were using |
@nargiza-sarkulova FYI - you can get around this issue by using the |
@e-dard Sorry for not being clear about using |
Can you guys confirm that you fixed this issue only for DELETE but not for DROP? Is it correct behavior that DROP SERIES WHERE tag=value should not work with tsi1? |
@derrley what release version are you using? It should work AFAIK. However in |
@e-dard we got it working! query bug. |
I'm using influxdb to record sensors and every once in a while I get insane values, like that my house was using 1 Megawatt:
These values throw off all my charts by scaling them insanely and also ruin |
InfluxDB shell version: 1.8.10 |
|
What's wrong with my query? |
Bug report
System info:
OS: Ubuntu 16.10
InfluxDB 1.3.1 & 1.3.2 (pre-built package)
Steps to reproduce:
curl -i http://localhost:8086/query -u root:root --data-urlencode "q=CREATE DATABASE mydb"
curl -i -XPOST 'http://localhost:8086/write?db=mydb' -u root:root --data-binary 'temperature,instrument_id=1 value=25 1422568543702900257'
DELETE FROM temperature WHERE instrument_id='1' AND time > '2015-01-29 20:00:00'
Expected behavior:
Record is deleted.
Actual behavior:
The above error.
Additional info:
If I omit either tag constraint or time constraint it works. This exact query used to work before I upgraded InfluxDB to newer version.
The text was updated successfully, but these errors were encountered: