Influxdb: Retention policy scope for delete commands

[kostasb]

Feature request: Support retention policy scope for series deletion commands such as DROP MEASUREMENT , DROP SERIES , DELETE FROM.

Current behavior: Delete commands have database-wide scope. As a result, it is not possible to delete a measurement under a specific retention policy without having it deleted from all retention policies in the database it lives in.

Consider:

db1.rp1.measurement
db2.rp2.measurement

There is currently no way to drop the measurement or some series of it, from a specific rp.

[jwyse]

+1

[ryantheleach]

Oh man.

This thoroughly confused me when attempting to delete data. (on 1.3, due to supported libraries on .net)

1. Chronograf fails to parse

DELETE FROM /.*/ WHERE "time" >= '2018-02-28T02:26:08.0000000Z' AND "time" <= '2018-02-28T02:27:08.0000000Z'

database not found

DELETE FROM "SensorData"../.*/ WHERE "time" >= '2018-02-28T02:26:08.0000000Z' AND "time" <= '2018-02-28T02:27:08.0000000Z'

received status code 400 from server: err: error parsing query: database not supported at line 1, char 1

When it works fine from command line as no database was specified, yet if you specific a database, it fails.

Additionally this prevents me from having a slightly more flexible schema.
https://stackoverflow.com/questions/49022407/how-can-i-delete-measurements-within-a-time-range-for-a-given-rp

[EugenNY]

this missing feature makes the use of retention policies and CONTINUOUS QUERIES hardly usable...

[fanjun1980]

+1

[alespour]

+1

[nicolas17]

I created a few RPs to store aggregated data, created CQs to put new data in them, and backfilled them with some SELECT..INTO queries. Now I want to delete the old high-resolution data from the default RP.

• If I use DELETE FROM telegraf.autogen.cpu WHERE time < now() - 30d, I get "ERR: error parsing query: retention policy not supported" (ie. this bug).
• If I use DELETE FROM cpu WHERE time < now() - 30d, I would delete old cpu data for all RPs, including what I just aggregated.
• If I alter the autogen RP to retain data for 30 days, I would delete old data for all measurements in the autogen RP rather than only cpu.

Looks like the only solution is to do the aggregated backfilling for _all_ my measurements and only alter the RP when I'm completely done... for which I'll have to give my server a bigger disk first :sparkles:

[lansalot]

This is a pretty serious hole - any ETA for implementation?

[akamac]

Any roadmap for this feature?

[xPaw]

This is silly.

I did use database.autogen which said it switched to the database using a retention policy, and then drop measurement name which ended up deleting data from autogen AND another retention policy I had.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically closed because it has not had recent activity. Please reopen if this issue is still important to you. Thank you for your contributions.

[akamac]

This needs to be reopened and addressed.

[hanynowsky]

Oh My goodness.
I cam across this issue to day when I had to delete some data from the default retention and the from another downgraded retention.
And all I get is:
ERR: error parsing query: retention policy not supported at line 1, char 1

This is a high priority issue.

What is the point of DELETE if it cannot be applied to retention policies.

[andydavidson]

'wontfix'ing this is sinful.

[James00001]

Yes, clearly "stale bot" closed this one in error, someone with the authority to do so needs to mark this as re-opened.

[foobar]

still needed

[dgnorton]

Re-opened. This issue was closed automatically for being stale but is a valid issue.