You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when we update some of the catalog parameters, Gravitino just updates the parameters without doing others. So the new parameters cannot take effect. A simple scenario is that:
When we create a MySQL catalog with wrong jdbc URL, it doesn't work even after we alter the catalog with new parameter. What currently we can do is to delete the old catalog, and create a new one with the correct parameter.
This is very inconvenient.
Motivation
No response
Describe the solution
We should support rebooting the catalog when the catalog is altered. Since this is a pretty large work, we should have a concrete design before doing.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the feature
Currently, when we update some of the catalog parameters, Gravitino just updates the parameters without doing others. So the new parameters cannot take effect. A simple scenario is that:
When we create a MySQL catalog with wrong jdbc URL, it doesn't work even after we alter the catalog with new parameter. What currently we can do is to delete the old catalog, and create a new one with the correct parameter.
This is very inconvenient.
Motivation
No response
Describe the solution
We should support rebooting the catalog when the catalog is altered. Since this is a pretty large work, we should have a concrete design before doing.
Additional context
No response
The text was updated successfully, but these errors were encountered: