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
When we create a sharded table with Buddy, we must ensure that users are not allowed to directly alter, modify, or delete this table.
These operations should be performed exclusively by Buddy because the table is distributed and contains multiple shards. To maintain consistency in the sharding mechanism, users can only read and write. Alterations should only be allowed through the Buddy process and method we designate.
We could implement the drop table feature with Buddy by adding a protection mechanism on the daemon side. This mechanism would throw an error if we try to modify a table without Buddy's involvement. Since the operation is routed through Buddy, it can perform all the necessary actions to maintain consistency when removing it.
Before, we were planning to use the DROP SHARDED TABLE syntax, but based on our latest discussion, it seems we could stick with the default syntax.
When we create a sharded table with Buddy, we must ensure that users are not allowed to directly alter, modify, or delete this table.
These operations should be performed exclusively by Buddy because the table is distributed and contains multiple shards. To maintain consistency in the sharding mechanism, users can only read and write. Alterations should only be allowed through the Buddy process and method we designate.
This issue is currently blocked by: manticoresoftware/manticoresearch#1423
The text was updated successfully, but these errors were encountered: