[
https://issues.apache.org/jira/browse/CASSANDRA-7807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Stupp updated CASSANDRA-7807:
------------------------------------
Attachment: 7807-v2.txt
I’ve added functionality to {{SimpleClient}} to specify the requested protocol
version (also added support for that to {{Client}}/{{debug-cql}} tool).
The code now
* checks for protocol version 4 (added utest)
* checks if the connection registered for the event (added negative utest)
* ensure that event is not sent when tracing probability kicks in (added utest)
* added {{minimumVersion}} field to {{Event.Type}} enum
* also enhanced {{MessagePayloadTest}} to check behavior with native protocol <
4 (CASSANDRA-8553)
* also enhances {{debug-cql}} to specify native protocol version + event display
NB: {{debug-cql}} did not start when C* is running locally (port 7199 used),
since it sources {{cassandra-env.sh}}
> Push notification when tracing completes for an operation
> ---------------------------------------------------------
>
> Key: CASSANDRA-7807
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7807
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: Tyler Hobbs
> Assignee: Robert Stupp
> Priority: Minor
> Labels: client-impacting, protocolv4
> Fix For: 3.0
>
> Attachments: 7807-v2.txt, 7807.txt
>
>
> Tracing is an asynchronous operation, and drivers currently poll to determine
> when the trace is complete (in a loop with sleeps). Instead, the server
> could push a notification to the driver when the trace completes.
> I'm guessing that most of the work for this will be around pushing
> notifications to a single connection instead of all connections that have
> registered listeners for a particular event type.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
