[
https://issues.apache.org/jira/browse/CASSANDRA-21045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-21045:
----------------------------------------
Attachment: ci_summary.html
result_details.tar.gz
> Schema comments and security labels aren't included in schema element
> comparisons
> ---------------------------------------------------------------------------------
>
> Key: CASSANDRA-21045
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21045
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Fix For: 6.x
>
> Attachments: ci_summary.html, result_details.tar.gz
>
>
> Adding and altering {{COMMENT}} and {{SECURITY LABEL}} at the keyspace,
> column, user type or field levels don't produce any output from
> {{Keyspaces::diff}} which determines the extent and scope of any schema
> change. Table level comments and security labels work as expected.
> This has several effects:
> * The new DDL statements return incorrect response messages to clients:
> {{ResultMessage.Void}} not {{ResultMessage.SchemaChange}}
> * No schema change notifications are triggered for these events
> * Following CASSANDRA-21001, DDL statements which produce no effect on the
> coordinator are not submitted to the CMS. Because the {{COMMENT ON...}} and
> {{SECURITY LABEL ON...}} statements produce an empty {{{}KeyspacesDiff{}}},
> none are ever submitted to the CMS and so can never be applied.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
