Thanks Ben, I found that thread, but my concern is the inconsistency on the Cassandra side. Why is the protocol ID correct for some tables but not others? Why does it work when I do a clean install on a new 2.0.x cluster? The bug seems to be on the Cassandra side and the clients seem to just be providing patches to these issues.
I will post to the Datastax java driver mailing list and see if they are willing to add a patch. -Karl > On Jul 18, 2014, at 3:59 AM, Ben Hood <0x6e6...@gmail.com> wrote: > >> On Fri, Jul 18, 2014 at 3:38 AM, Karl Rieb <karl.r...@gmail.com> wrote: >> Any suggestions on what is going on or how to fix it? > > I'm not sure how much this will help, but one of the gocql users > reported similar symptoms when upgrading to 2.0.6. We ended up > applying a client side patch to address the issue, the details are > here: > > https://github.com/gocql/gocql/pull/154 > > That pull request also references the original bug report: > > https://github.com/gocql/gocql/issues/151 > > Not sure how helpful this will be though.
