The selection of the bucket in the “Data Explorer” delivers this table
|table|_measurement|_field|_value|_start|_stop|_time|
|0|Zaehlerstand|Terrarien|49.5465|2023-02-09T16:16:05.550Z|2023-02-10T16:16:05.550Z|2023-02-09T20:16:00.000Z|
|0|Zaehlerstand|Terrarien|49.5465|2023-02-09T16:16:05.550Z|2023-02-10T16:16:05.550Z|2023-02-09T20:20:00.000Z|
So the relevant dates are “2023-02-09T20:16:00.000Z” and “2023-02-09T20:20:00.000Z”.
Then i build these two stmts with ±1 minute:
influx delete --bucket Zaehlerstaende --start 2023-02-09T20:15:00.000Z --stop 2023-02-09T20:17:00.000Z
influx delete --bucket Zaehlerstaende --start 2023-02-09T20:15:00.000Z --stop 2023-02-09T20:17:00.000Z
Looks good: No error occurs. But the values were not deleted afterwards.
I’ve tried it with a “–token …” and “” with no change.
then I deleted the data using this command: influx delete --bucket webbreaks --start 2023-02-27T10:05:24Z --stop 2023-02-27T11:05:25Z , (“webbreaks” is my bucket) The Problem: is that once I deleted the data I still see this
And I cannot ingest data again. As a summary, it looks like the command is deleting the data but not completely. I have tried repeating the ingestion process but just get the empty headers, Meaning that I cannot longer ingest CSV data from files. @Anaisdg could you maybe point us to someone on your team who can give us more input on this please?
First I had to disable “mean” in the Data Explorer to get the real date in UTC. “Mean” is enabled automatically.
In addition, the token was missing in the statement.
The relevant time was: 2023-02-09 20:17:01 UTC
So I came to the following statement
Only with the this combination the data was finally deleted.
It is annoying that you don’t get any feedback how many records were deleted or you just didn’t get access. This could be solved much better!
After all data is deleted during this time, I will test it next time with --predicate '_field="FIELD"'