[
https://issues.apache.org/jira/browse/CASSANDRA-7881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Stupp updated CASSANDRA-7881:
------------------------------------
Attachment: 7881.txt
Attached patch and branch on github.
* Adds {{schemaVersion}} to {{SchemaChange}} event/response.
* Had to change when {{Schema.updateVersion()}} gets called to ensure that
events and response communicate the correct version.
* Added a new unit test that explicitly tests schema change version in event +
response
* Also fixed {{CQLTester}}/{{UFTest}} only to use protocol versions that the
Java driver supports
* Noticed that much effort spent to optimize reads in
{{LegacySchemaTables.mergeSchema}} is torpedoed by generating the
schemaVersion, which has to read the whole schema. We could optimize that a
after 8099 has landed.
> 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: 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)
