[
https://issues.apache.org/jira/browse/CASSANDRA-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-21001:
----------------------------------------
Source Control Link:
https://github.com/apache/cassandra/commit/44f6a3271888300546172563069372fba617ab9c
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Don't submit AlterSchemaStatements which produce no effect locally to the CMS
> -----------------------------------------------------------------------------
>
> Key: CASSANDRA-21001
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21001
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Fix For: 6.x
>
> Attachments: ci_summary.html, pre-ci.c.a.o-ci_summary.html,
> pre-ci.c.a.o-results_details.tar.xz, result_details.tar.gz
>
>
> If a DDL statement produces no effect when the coordinator performs the
> pre-submission application of the schema transformation, we can skip sending
> it to the CMS and return a Void response.
> The initial implementation would submit any {{AlterSchemaStatement}} which
> did not generate an error but this can lead to many DDL operations which are
> in fact no-ops being committed to the log. One example would be a client
> application which performs a series of DDL statements with {{IF NOT EXISTS}}
> clauses whenever it starts up. This is strictly correct, as the operations
> will all be no-op'd when applied by the nodes in the cluster, but is somewhat
> wasteful and not intuitive.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
