In case someone stumbles upon this same thing later. Ended up being a collection item that was too big (i.e., larger than 64K). Something to do with the way Cassandra generates the keys for collections, but moving the offending collection from a list<UDT> to a separate clustering key solved this particular instance. The error message could definitely be better though, and I'll raise it with the devs.
Regards, Emils On Wed, 9 Mar 2016 at 20:31 Emīls Šolmanis <emils.solma...@gmail.com> wrote: > Hey Alex, > > I did do a grep for that message in the driver code base and it seems like > it's not there, so I think this is coming from the server. > > Only thing I can think of is us exceeding one of the limits (e.g., the 65K > collection item one) and then the error message being super misleading. > I'll check the server code tomorrow and see if I can track that message > down. > > Regards, > Emils > > On Wed, 9 Mar 2016 20:02 Alex Popescu, <al...@datastax.com> wrote: > >> Hi Emīls, >> >> Directing this question to the Java driver mailing list will give you >> better chances to get an answer: >> https://groups.google.com/a/lists.datastax.com/forum/#!forum/java-driver-user >> >> (as a side note, I haven't seen this one before) >> >> On Wed, Mar 9, 2016 at 11:52 AM, Emīls Šolmanis <emils.solma...@gmail.com >> > wrote: >> >>> Hello, >>> >>> I keep getting an exception about a clustering key being too long, like >>> >>> com.datastax.driver.core.exceptions.InvalidQueryException: The sum of all >>> clustering columns is too long (72650 > 65535) >>> at >>> com.datastax.driver.core.Responses$Error.asException(Responses.java:136) >>> at >>> com.datastax.driver.core.DefaultResultSetFuture.onSet(DefaultResultSetFuture.java:179) >>> at >>> com.datastax.driver.core.RequestHandler.setFinalResult(RequestHandler.java:184) >>> >>> >>> But the table has no clustering key. Even if I set the clustering key to >>> a single column that's guaranteed to be a string around 4-5 characters, I >>> get the same thing. >>> >>> The only result Google gave me suggested this was about the clustering >>> key names, so I renamed all the fields in the schema def to 1-3 letters, to >>> no avail. >>> >>> Does anyone know what this is about and how I can solve this? >>> >>> Running Cassandra 2.2.4, Datastax driver 3.0.0. >>> >>> Regards, >>> Emils >>> >> >> >> >> -- >> Bests, >> >> Alex Popescu | @al3xandru >> Sen. Product Manager @ DataStax >> >>
