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 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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: