[
https://issues.apache.org/jira/browse/CASSANDRA-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275488#comment-14275488
]
Jorge Bay commented on CASSANDRA-7679:
--------------------------------------
Sorry guys, dismiss my comment (insert a shame meme here): The wait for the
schema agreement after a schema change response was never implemented in the C#
driver and I though it was the common behaviour across all drivers.
> Batch DDL
> ---------
>
> Key: CASSANDRA-7679
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7679
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Robert Stupp
>
> Just an idea: To improve speed of DDL in clusters with lots of
> Keyspaces/Tables/Columns it might help to collect a bunch of schema changes
> and propagate them as a single bunch of changes.
> Such a DDL batch would
> # execute DDLs locally and collect all mutations
> # broadcast all mutations at once
> # schema agreement
> # return list<SchemaChange> via native protocol to the client
> So {{DefsTables.mergeSchemaInternal}} (which seems to be the expensive part)
> would only execute once per DDL batch on each node.
> DDL batches would not be atomic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
