Petrit created CASSANDRA-20991:
----------------------------------
Summary: Drop table vs truncate table commands behaviors
Key: CASSANDRA-20991
URL: https://issues.apache.org/jira/browse/CASSANDRA-20991
Project: Apache Cassandra
Issue Type: Bug
Components: Consistency/Coordination
Reporter: Petrit
We are experimenting with drop table and truncate command and are observing
conflicting behaviors while having nodes down.
Drop table is able to execute even though nodes are down, if the dropped table
is later re-created it will get a new schema ID assigned.
However, truncate requires all nodes to be up for truncate to work. Even though
the nodes are not part of the replicas for the keyspace.
Is this expected behavior for the two commands? I would expect the following:
- Truncate to only require replicas of the keyspace to be up
- Drop table to require all nodes to be up as schema ID is re-created (if table
is re-created)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
