Replies: 1 comment
-
Hey, I second this. The biggest missing piece for me in QuestDB right now is an automated retention policy. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
According to data retention section of the doc, the data retention policy on questdb is implemented as drop-able partitions. While this is flexible to implement custom policy of expiry, I still miss influxdb's straight-forward way: defining data retention policy, delete expired data automatically. It requires no additional cronjob or operation script to keep the database sustaining.
The idea is to add a
MAX_PARTITIONS
option toCREATE TABLE
command:So that partitions are deleted in a FIFO manner when its count exceeds 30.
Beta Was this translation helpful? Give feedback.
All reactions