[CASSANDRA-7881] SCHEMA_CHANGE Events and Responses should carry the Schema Version

• Type: Sub-task
• Status: Resolved
• Priority: Low
• Resolution: Won't Fix
• Labels: protocolv4
• Impacts: Clients
• Assignee: Robert Stupp Assign to me
• Reporter: Michaël Figuière

Authors

Robert Stupp

• Created: 05/Sep/14 00:17
• Updated: 06/Nov/19 21:58
• Resolved: 31/Mar/16 16:25

Description

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.

Issue Links

• links to: Git branch