You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (Jira)" <ji...@apache.org> on 2020/12/15 18:03:00 UTC
[jira] [Updated] (CASSANDRA-16353) Fix client push notifications in
protocol v5
[ https://issues.apache.org/jira/browse/CASSANDRA-16353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sam Tunnicliffe updated CASSANDRA-16353:
----------------------------------------
Bug Category: Parent values: Degradation(12984)Level 1 values: Other Exception(12998)
Complexity: Normal
Discovered By: Unit Test
Severity: Normal
Status: Open (was: Triage Needed)
> 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
>
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org