-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[exporter/clickhouse] Add support for short data TTL #28675
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This makes sense. I think TTL should be |
I will give it a try in my spare time. To be honest, I have limited experience in contributing to open-source projects and working with Golang, so it may take some time. |
Timeline is not a problem. I don't think anyone else is interested in this. I can still put a |
I will make this change within this week, or next week at the latest. |
…trol (open-telemetry#29095) **Description:** Added support for more control over TTL configuration. Currently, it supports timelines only in days, and now also in hours, minutes and seconds. **Link to tracking Issue:** [28675](open-telemetry#28675)
Component(s)
exporter/clickhouse
Is your feature request related to a problem? Please describe.
I want to save disk space by reducing retention to several hours, which is more than enough for me. I cannot achieve this without manual schema migration or complex workarounds.
Describe the solution you'd like
It would be great to have the possibility to configure TTL by using a ttl_hours parameter instead of ttl_days if the duration is less than a day.
Describe alternatives you've considered
I have considered more general alternative approaches:
Additional context
No response
The text was updated successfully, but these errors were encountered: