I second Brandon. There is a group of people who expect to ssh into a node and then be able to run the "right" cqlsh instead of dealing with different cqlsh versions on their workstation/laptop...
German ________________________________ From: Brandon Williams <dri...@gmail.com> Sent: Friday, August 11, 2023 7:29 AM To: dev@cassandra.apache.org <dev@cassandra.apache.org> Subject: [EXTERNAL] Re: [Discuss] CEP-35: Add PIP support for CQLSH On Fri, Aug 11, 2023 at 2:13 AM Miklosovic, Stefan <stefan.mikloso...@netapp.com> wrote: > > If we had an official PIP package, I can imagine that we would not ship CQLSH > in RPM at all (maybe not in DEB either?) so we would decouple this. A PIP > package is installable almost anywhere (if it is Python 3, that is the way > how I solved the problem in 18642, I just installed a PIP package because RPM > installation was broken). I don't think we want to ship the database without any way to interact with it. Pip may also not be accessible to all installations. > Another problem I see is that how do we say what CQLSH is compatible with > what Cassandra release? If we shipped CQLSH as a PIP package as part of the > tarball, we would guarantee that they play together. If it is living > somewhere online, how can be people sure that what they install is compatible > with Cassandra they run? I am sorry if this was already explained somewhere. It is only guaranteed to work with the version it shipped with. It may work with other versions, or it may have subtle issues that you could spend a lot of time trying to figure out, as German and I recently discovered. To that end, I've created CASSANDRA-18745 so at least you will know to expect problems when the versions don't match.
