14

My OSX install of Cassandra seems to have been broken by yesterday's release. Cassandra seems to start OK.

Jeremys-MacBook-Pro: fractal jeremy$ cqlsh --version
cqlsh 5.0.1



Jeremys-MacBook-Pro:fractal jeremy$ cqlsh localhost
Traceback (most recent call last):
  File "/usr/local/Cellar/cassandra/3.11.2/libexec/bin/cqlsh.py", line 2443, in <module>
    main(*read_options(sys.argv[1:], os.environ))
  File "/usr/local/Cellar/cassandra/3.11.2/libexec/bin/cqlsh.py", line 2421, in main
    encoding=options.encoding)
  File "/usr/local/Cellar/cassandra/3.11.2/libexec/bin/cqlsh.py", line 488, in __init__
    **kwargs)
  File "cassandra/cluster.py", line 735, in cassandra.cluster.Cluster.__init__ (cassandra/cluster.c:10935)
TypeError: __init__() got an unexpected keyword argument 'no_compact'
aL_eX
  • 1,453
  • 2
  • 15
  • 30
Jerry Taylor
  • 161
  • 4

3 Answers3

24

I just commented this line 488: #no_compact=no_compact, in file /usr/local/Cellar/cassandra/3.11.2/libexec/bin/cqlsh.py and it works again.

bungle
  • 424
  • 2
  • 3
  • 2
    I had five references to this littered in that file, had to comment them all out and it works as well – nbpeth Feb 26 '18 at 23:46
  • 2
    It is line 483 for me, just installed via brew, but that worked for me as well – Nick Mar 06 '18 at 15:08
  • I just commented 3 `no_compact=False`, and `cqlsh` finally started. Thanks for help! Hoping those commented lines won't break something else… – Ivanka Eldé Apr 05 '18 at 12:20
0

I also had this issue. My current workaround was to install cqlsh via pip, and then run Cassandra (ScyllaDB in our case) via a docker container.

You can file an issue here.

Dan Sexton
  • 13
  • 3
0

csqlsh was not broken in the 3.11.2 release of Cassandra. However, the Homebrew formula for the 3.11.2 release was originally broken, per Homebrew issue 24977. Per that ticket and CASSANDRA-14301, Homebrew was configured to use the wrong version of the Cassandra Driver, which was using an incompatible version of Python.

This has since been fixed in Homebrew, so new installations of 3.11.2 should not have this issue.

M. Justin
  • 14,487
  • 7
  • 91
  • 130