[
https://issues.apache.org/jira/browse/CASSANDRA-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934705#comment-13934705
]
Sylvain Lebresne commented on CASSANDRA-6236:
---------------------------------------------
I did wrote a version of the native protocol with Netty 4 back in the days. At
the time, Netty 4 was still alpha so I left that aside, but for reference the
code of that is at
https://github.com/pcmanus/cassandra/commit/a4aaa08a6a4b9ebdfb73b588b0dacea31cad8472.
It's obviously outdated, and it's even possible that Netty 4 got a few changes
between the version that was used on that branch and the final, but that gives
an idea of what's involved and rebasing from that shouldn't be too involved.
I'll note that while Netty 4 does have a fair amount of API changes compared to
Netty 3, a lot of it is rather cosmetic (ChannelBuffer renamed to ByteBuf) and
I don't think it will be a very complex change. So I wouldn't necessarily make
this a blocker for 2.1, but if we find the time to do it, I wouldn't oppose
having it there. And truly, I'm not sure this is a change that *has to* be in a
major, 2.1.1 would be fine imo if we're a bit short on time for 2.1 and want a
little bit more time to test.
Regarding Netty 5, we should of course upgrade to that once it's final and
tested, but from what I've seen the changes there are rather incremental over
Netty 4 so I don't think we're wasting much time in upgrading to Netty 4 in the
meantime.
> Update native protocol server to Netty 4
> ----------------------------------------
>
> Key: CASSANDRA-6236
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6236
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sylvain Lebresne
> Assignee: Benedict
> Priority: Minor
> Fix For: 3.0
>
>
> We should switch to Netty 4 at some point, since it's the future.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
