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

Handle when a node has a table that the manager does not have on start-up #252

Open
CGodiksen opened this issue Oct 26, 2024 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@CGodiksen
Copy link
Collaborator

Currently when starting a node and connecting to the manager, we check if the node has any tables that the manager does not have. If that is the case, we throw an error and stop the server. Since we now support dropping tables, it is possible to instead just drop the tables that are not in the cluster database schema and avoid throwing an error.

When implementing this, we should also consider adding a check for the schema of the existing tables to ensure that we handle the case where a node already has a table with the same name as a table in the cluster database, but the tables have different schemas.

@CGodiksen CGodiksen added the enhancement New feature or request label Oct 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant