Allow the specification of a write window for retention policies #25424
Assignees
Labels
1.x
area/data ingestion
Issues related to any type of data ingestion/acquisition
area/influxql
Issues related to InfluxQL query language
area/retention policies
Comments
davidby-influx
added
area/retention policies
area/influxql
davidby-influx
added a commit
that referenced
this issue
Oct 3, 2024
Add FutureWriteLimit and PastWriteLimit to retention policies. Points which are outside of now() + FutureWriteLimit or now() - PastWriteLimit will be rejected on write with a PartialWriteError. closes #25424
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Customer operating "shared" clusters frequently run into issues where a user will attempt to write data in to the cluster and the time is skewed either deeply into the future or significantly into the past.
Clean-up of this "bad data" is then problematic, time consuming, etc.
Add
FutureWriteLimitandPastWriteLimitto retention policies. Points which are outside of now() + FutureWriteLimit or now() - PastWriteLimit will be rejected on write with a PartialWriteError.The default will be zero for both values, which behaves as the current product.
There will be corresponding work for Enterprise and InfluxQL.
The text was updated successfully, but these errors were encountered: