[
https://issues.apache.org/jira/browse/CASSANDRA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296489#comment-15296489
]
Robert Stupp commented on CASSANDRA-7190:
-----------------------------------------
bq. CREATE OR REPLACE then have same meaning as DROP IF EXISTS and CREATE
Well, the idea for this was: If the table already exists, apply the changes. If
it doesn't already exist, just create it. So, not a DROP IF EXISTS + CREATE.
But yea, we should probably go with {{ALTER TABLE DROP ... WITH TIMESTAMP}}
first. Or something like {{ALTER TABLE ADD ... WITH TIMESTAMP}} (which would
add a column but also add an entry to the deleted-columns list).
On the long run, a DDL batch would be beneficial, but I think that's stuff for
a separate ticket. If we have all DDL statements for the keyspace and the
table(s), it would be a no-brainer to bundle these into a batch.
bq. only problem I currently see is Materialized Views
I think you're referring to MVs being built and/or having pending updates in
some batch log. I *think* that would be fine with a sequence of individual DDL
statement - but not sure. Maybe [~tjake] or [~carlyeks] know.
> Add schema to snapshot manifest
> -------------------------------
>
> Key: CASSANDRA-7190
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7190
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Jonathan Ellis
> Assignee: Alex Petrov
> Priority: Minor
> Labels: lhf
> Fix For: 3.x
>
>
> followup from CASSANDRA-6326
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
