cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7679) Batch DDL
Date Sun, 03 Aug 2014 16:36:12 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084024#comment-14084024
] 

Aleksey Yeschenko commented on CASSANDRA-7679:
----------------------------------------------

Not a new idea, but we are going to keep fighting it and similar ones for as long as we can.
Because if batch DDL is a solution to your problem, then you are using Cassandra wrong.

> 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.2#6252)

Mime
View raw message