“ 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
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
: [EXTERNAL] [Discuss] CQLSH confusion
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 f
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 distribu
