Good call! Java client was using Cassandra 2.11 lib jars in classpath. Switching to Cassandra 3.11 jars in Java client classpath works!
Thx! Lou. On Thu, Apr 26, 2018 at 10:30 AM, Michael Shuler <mich...@pbandjelly.org> wrote: > On 04/26/2018 09:17 AM, Lou DeGenaro wrote: > > > > I started fresh and edited the 3.11 cassandra.yaml file. Here are the > > exact changes: > > > > diff cassandra.yaml cassandra.yaml.orig > > 425c425 > > < - seeds: "bluej421" > > --- > >> - seeds: "127.0.0.1" > > 599c599 > > < listen_address: bluej421 > > --- > >> listen_address: localhost > > 676c676 > > < rpc_address: bluej421 > > --- > >> rpc_address: localhost > > > > I made no other changes to Cassandra. After launching server, cqlsh > > client works. > > cqlsh uses embedded python driver. Good check, server is running. > > > My java client fails just the same. > > Check your java driver version is compatible with your version of > Cassandra. See Andy Tolbert's comment on > https://datastax-oss.atlassian.net/browse/JAVA-1092 > > The system tables changed in 3.0+. > (I hope this guess is close than my last couple :) ) > > -- > Michael > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org > >
