-
Notifications
You must be signed in to change notification settings - Fork 200
Configuration property 'catalog.config-dir' was not used #332
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
Comments
I can't reproduce this using the following commands:
|
Thank you for looking to the issue. What might be the issue from my side? I want to use the dynamic catalog functionality and I receive the error on a coordinator. My full yaml
Kubernetes error. The K8 cluster is run in Rancher.
Thank you. |
The docs for this property say:
See #178 for an example how to enable dynamic catalogs. |
Hi @nineinchnick, Your sample was critical for me to understand the dynamic catalog setup. I appreciate your information! The issue is in something else. I'm still receiving the same issue. It seems Trino coordinator doesn't recognize I'm missing something what I can't get. If you could look your fresh eyes? Persistent storage: catalogs-pvc.yaml
Create persistent storage
Values: values-dev.yaml
Create deployment
Validate pods
Output
Coordinator log
Thank you! |
I have success with the configuration to store catalogs in memory
|
What would be the best approach to resolve my issue with dynamic catalog file storage ( |
I just encountered the same issue when trying to get it to work in kubernetes. Can we reopen this issue please? |
@IcaroG I was not aware of that, thanks for pointing it out! |
The confusion comes from
|
I would argue that this is not an issue with the chart itself, but with the documentation at https://trino.io/docs/current/admin/properties-catalog.html You can correctly set it up with the chart with this config:
|
Thank you, @IcaroG, for your research. I tried it and it seems working but I couldn't make it work completely. When I create a dynamic catalog, I get "Could not store catalog properties" error. The error is caused by the mount permissions.
Root only has write access to the mount. I'm not sure how to change it. |
To fix the permission issue you just need to add
There are other ways too, like initContainers, but this is how I did it. |
It works for me. I appreciate your help @IcaroG. |
Hello,
When I try to use
catalog.config-dir
property for coordinator, "Configuration property 'catalog.config-dir' was not used" error is encountered.Sample of the configuration
Thanks.
The text was updated successfully, but these errors were encountered: