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
We should add functionality to support dropping shared tables. The command should clean up everything associated with the shared table. To make this happen, we should start with a special command DROP SHARDED TABLE. After that, we'll migrate to use the DROP TABLE command, while the daemon should detect if it's a shared table or not and process the request accordingly.
This requires modifications on the daemon side, so we'll start with the DROP SHARDED TABLE syntax first.
The text was updated successfully, but these errors were encountered:
donhardman
changed the title
Create issues about DROP SHARDED TABLE and a special flag to ease routing of a DROP TABLE to Buddy
DROP sharded table
Apr 29, 2024
During the implementation of the DROP SHARDED TABLE logic, a requirement also arose to refactor our old system with hooks. As a result, I made changes in the core and placed code in the appropriate locations. The QueryProcessor is now much cleaner, and the common logic for using processors of each plugin has become clearer.
We should cover that DROP SHARDED TABLE x works fine for both single sharded and clustered environment.
That means just implement various check that executes DROP SHARTED TABLE x for different tables (also not sharded) and make sure that it works ONLY for those that sharded
We should add functionality to support dropping shared tables. The command should clean up everything associated with the shared table. To make this happen, we should start with a special command
DROP SHARDED TABLE
. After that, we'll migrate to use theDROP TABLE
command, while the daemon should detect if it's a shared table or not and process the request accordingly.This requires modifications on the daemon side, so we'll start with the
DROP SHARDED TABLE
syntax first.The text was updated successfully, but these errors were encountered: