I would suggest that you do not dynamically alter table schemas as part of your data model. Cassandra is a series-oriented database partitioned and clustering strings in partitions. Thus, everything that you are trying to imagine adding or removing columns is best handled by setting values ββin a fixed set of columns.
Although Cassandra allows you to change the table definitions for adding and removing columns, this is usually done only when adding a new function to the application, so you must manually change the scheme, and then use the modified application code to use the new scheme.
I consider it dangerous for a client application to modify a schema by creating or modifying tables, since you run the risk of multiple clients making changes at the same time.
source share