“ keep the C* version somewhere in cqlsh and warn when it doesn't match the server.”
+1 on this suggestion. I had horrible experience recently with things changing their versioning in another project. It brings mostly confusion. Warning and adding C* version makes it simple and obvious. No need to dig into docs, tickets, PRs On Thu, 13 Jul 2023 at 13:26, Brandon Williams <dri...@gmail.com> wrote: > You forgot to link references, > https://issues.apache.org/jira/browse/CASSANDRA-18666 has it all > though I think > > I think it's too late to align versions, that cat is out of the bag. > What we can do though is what I last suggested there: keep the C* > version somewhere in cqlsh and warn when it doesn't match the server. > > Kind Regards, > Brandon > > On Thu, Jul 13, 2023 at 12:14 PM German Eichberger via dev > <dev@cassandra.apache.org> wrote: > > > > All, > > > > I am working with clusters with different Cassandra versions and have > been using some cqlsh which "just worked". Recently I wanted to use virtual > tables and ran into [1]. After that I filed [2]. > > > > Brandon states that "do not use a cqlsh that is from a different version > than what is distributed with the server" since I have no idea what other > incompatibilities like this there are, compatibility of that kind has never > been a goal." > > > > I would like to open the discussion if this is what we want: cqlsh needs > to be in lockstep with the C* version. > > > > Assuming, this is how things should be, I would propose to change the > cqlsh versioning to be in line with the C* versioning. Right now I am using > cqlsh 6.0.1 and I have no idea to which C* version that translates to. > Aligning versions would make this much easier. > > > > Thanks, > > German >
