feat: Adding retention policy scoped deletes to v1 queries #27072
+400
−23
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR is a "cherrypick" of the functionality from: #25312 Albeit influxdb2 regularly has single retention periods per bucket, where as influxdb1 can have many retention policies per database. There is some backwards compatibility built in to v2 that includes the DBRP mapping functionality: https://docs.influxdata.com/influxdb/v2/api-guide/influxdb-1x/dbrp/#when-creating-a-bucket This PR will add functionality that allows for queries like `delete from rp2.new_measurement WHERE time > 0` to work, previously this query would delete the measurement from the default 'autogen' rp instead of 'rp1' Closes #27040
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a "cherrypick" of the functionality from: #25312 influxdb2 regularly has single retention periods per bucket, where as influxdb1 can have many retention policies per database. There is some backwards compatibility built in to v2 that includes the DBRP mapping functionality: https://docs.influxdata.com/influxdb/v2/api-guide/influxdb-1x/dbrp/#when-creating-a-bucket
This PR will add functionality that allows for queries like
delete from rp2.new_measurement WHERE time > 0to work, previously this query would delete the measurement from the default 'autogen' rp instead of 'rp2'Closes #27040