[
https://issues.apache.org/jira/browse/CASSANDRA-16353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17249840#comment-17249840
]
Sam Tunnicliffe edited comment on CASSANDRA-16353 at 12/15/20, 6:09 PM:
------------------------------------------------------------------------
||branch||Circle CI||Apache CI||
|[16353-trunk|https://github.com/beobal/cassandra/tree/16353-trunk]|[circle|https://app.circleci.com/pipelines/github/beobal/cassandra?branch=16353-trunk]|[ci-cassandra|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/265/]|
was (Author: beobal):
||branch||CI||
|[16353-trunk|https://github.com/beobal/cassandra/tree/16353-trunk]|[circle|https://circleci.com/gh/beobal/cassandra?branch=16353-trunk]|
> 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
> Fix For: 4.0-beta
>
>
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
