[
https://issues.apache.org/jira/browse/CASSANDRA-7881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498512#comment-14498512
]
Robert Stupp commented on CASSANDRA-7881:
-----------------------------------------
LD;DR I'm not convinced we should do this at all.
Getting the scheme_version in a response or event does not buy anything.
Concurrent and consecutive DDLs will change the schema_version. IMO this means
that the schema_version from a response or event does not help in any way. The
only thing, that might help is to wait until the schema_versions of the
available nodes has settled - but even a newly joining or restarting node may
torpedo that at least temporarily. That may become even worse during a rolling
upgrade (not sure, but schema_changed events might occur during rolling
upgrades).
> SCHEMA_CHANGE Events and Responses should carry the Schema Version
> ------------------------------------------------------------------
>
> Key: CASSANDRA-7881
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7881
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Michaël Figuière
> Assignee: Robert Stupp
> Priority: Minor
> Labels: client-impacting, protocolv4
> Fix For: 3.0
>
> Attachments: 7881.txt
>
>
> For similar logging and debugging purpose as exposed in CASSANDRA-7880, it
> would be helpful to send to the client the previous and new schema version
> UUID that were in use before and after a schema change operation, in the
> {{SCHEMA_CHANGE}} events and responses in the protocol v4.
> This could then be exposed in the client APIs in order to bring much more
> precise awareness of the actual status of the schema on each node.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
