Skip to content
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

[FEATURE] Support catalog rebooting after altered #2267

Closed
jerryshao opened this issue Feb 20, 2024 · 1 comment · Fixed by #4262
Closed

[FEATURE] Support catalog rebooting after altered #2267

jerryshao opened this issue Feb 20, 2024 · 1 comment · Fixed by #4262
Assignees
Labels
0.6.0 Release v0.6.0 feature New feature or request

Comments

@jerryshao
Copy link
Contributor

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

@jerryshao jerryshao added the feature New feature or request label Feb 20, 2024
@jerryshao jerryshao added the 0.6.0 Release v0.6.0 label Aug 1, 2024
@yuqi1129
Copy link
Contributor

yuqi1129 commented Aug 1, 2024

Gravitino supports this functionality and this can be addressed by #4262

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.6.0 Release v0.6.0 feature New feature or request
Projects
None yet
2 participants