[
https://issues.apache.org/jira/browse/CASSANDRA-16353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-16353:
----------------------------------------
Fix Version/s: (was: 4.0-beta)
4.0
4.0-beta5
Impacts: Clients (was: None)
Since Version: 4.0-beta4
Source Control Link:
https://github.com/apache/cassandra/commit/c9d22583d22d566807e76fa10c65af29104ae16c
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Thanks, committed to trunk with the nit addressed.
> Fix client push notifications in protocol v5
> --------------------------------------------
>
> Key: CASSANDRA-16353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16353
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Labels: protocolv5
> Fix For: 4.0-beta5, 4.0
>
>
> The changes to native protocol v5 in CASSANDRA-15299 broke the delivery of
> push notifications from server to client. This wasn't caught earlier as there
> weren't any unit or dtests which would exercise client notifications in a
> beta protocol version. Working on CASSANDRA-14973 to bring v5 out of beta
> exposed the regression.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
