[ https://issues.apache.org/jira/browse/CASSANDRA-7881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Stupp resolved CASSANDRA-7881. ------------------------------------- Resolution: Won't Fix Fix Version/s: (was: 3.x) > 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 > 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)