I want to clear the data of a single data field. Unfortunately it doesn’t work with this code. The command in the CLI is accepted, but no data is deleted. There is also no error message.
influx delete \
--bucket test \
--start 1970-01-01T00:00:00Z \
--stop $(date +"%Y-%m-%dT%H:%M:%SZ") \
--predicate '_measurement="modbus" AND _field="Netzbezug Energie"'
If I take this code, the complete measurement “modbus” is deleted. Of course I don’t want that.
Quite the same here. Maybe something changed within the last 2 weeks, as the exact same command did the job for me two weeks ago. Not sure when the update from 2.6 to 2.6.1 happened, but maybe it has something to do with that?
Even without the additional tag it does not work
This is how my cli command looks like
influx delete --bucket MYDATABASENAME --start ‘2023-01-21T14:12:06.16Z’ --stop ‘2023-01-21T14:51:20.16Z’ --predicate ‘_measurement=“GasZaehlerStandAktuell”’ -o BCO -t MYADMINTOKEN
I have experimented with the timestamps, the apostrophes and the sequence of the commands. Absolutely nothing works.
I am on Influx 2.6.1 running within a LXC container. Strange enough, the exact same command worked for me 2 weeks ago… not that I am aware of any update of the DB since then.
The documentation states, that the “–predicate” parameter in 2.6.1 no longer allows deletion by “_field”, but “_measurement” should work. Unfortunately your post doesn’t explain why my example line of code (which seams very similar to what you posted) worked 3 weeks ago…
I was already playing with the times, with or without the nanoseconds, with times at 00:00 or different random values and with or without the different apostrophes. Nothing worked.
I tried to replicate your syntax as well, but without success.
As somebody stated in annother post, the “–o” and “–t” did not work for him, hence I testet “–org” and “–token” as well, which did not do anything as well. What really puzzles me the most is, that with the line of code above, no error is generated still no data is deleted. When I am playing around with the parametes, all sorts of errors are being generated (wrong date or time, missing credentials, etc). So it seems to me that the command itself is correct, but the DB engine just “doesn’t feel like” really executing anything…
Maybe it is a change between 2.6 and 2.6.1 ? But I am not sure when the update to 2.6.1 happened on my machine, hence I am speculating.