And as I said, that would be a bug in the driver that did this. Any driver implementing a protocol that has a “new” paging state, that supports mixed version connections, would need to handle that correctly and not send new states over the old protocol or old states over the new protocol.
As far as I know the current java driver does not support mixed protocol versions across its connections. So it would not need such logic. But and driver that supported mixed versions would need it. > On Sep 24, 2019, at 9:20 PM, Blake Eggleston <beggles...@apple.com.invalid> > wrote: > > Yes, but if a client is connected to 2 different nodes, and is using a > different protocol for each, the paging state formats aren’t going to match > if it tries to use the paging date from one connection on the other. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
