Alright ... so how I am interpreting this, even more so after Sam's and Brandon's mail, is that we should just get rid of that completely in trunk and deprecate in 5.0.
There are already patches for 3.x and 4.x branches of the driver so the way I was looking at that was that we might resurrect this feature but if there is actually no need for this then the complete removal in trunk is probably unavoidable. On Tue, Feb 13, 2024 at 1:27 PM Brandon Williams <dri...@gmail.com> wrote: > On Tue, Feb 13, 2024 at 6:17 AM Sam Tunnicliffe <s...@beobal.com> wrote: > > Also, if CASSANDRA-16999 is only going to trunk, why can't we just > deprecate dual ports in 5.0 (as it isn't at -rc stage yet) and remove it > from trunk? That seems preferable to shoehorning something into the new > system_views.peers table, which isn't going to help any existing drivers > anyway as none of them will be using it. > > I agree and I think it will be a mess having the port in 3.x, then not > in 4.0, 4.1, or 5.0, then resurrected again after that. > > Kind Regards, > Brandon >