-
Notifications
You must be signed in to change notification settings - Fork 7
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
Introduce CRD for Iceberg table maintanance #484
Comments
At the risk of killing this issue with scope-creep, we discussed having TrinoTable crds a while back that the operator would read and actually go and create the tables in Trino based on the information in there. If that hits, I think that object should contain the information described in this issue as well, not be put into a separate crd? |
Or well...thinking some more...we actually migth want to apply the same maintenance object to many tables .... |
Legit point, we should consider this when designing the CRD. I think it should be an ADR in any case |
Is this still in active development & is there already a release date determined? |
Hi @therealslimjp, sadly we did not start any work on this yet and I'm not aware of any ETA |
As a Trino Iceberg user I want to define a CR that allows me to regularly run maintenance actions on my tables.
Should
Could
One possible solution would be to create a k8s CronJob for every maintenance CR.
CRD could look something like
The text was updated successfully, but these errors were encountered: