Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9A19E18434 for ; Thu, 10 Mar 2016 17:39:37 +0000 (UTC) Received: (qmail 77395 invoked by uid 500); 10 Mar 2016 17:39:34 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 77355 invoked by uid 500); 10 Mar 2016 17:39:34 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 77345 invoked by uid 99); 10 Mar 2016 17:39:34 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Mar 2016 17:39:34 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id ED47CC6B8A for ; Thu, 10 Mar 2016 17:39:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id veaCRA4Q5AOs for ; Thu, 10 Mar 2016 17:39:32 +0000 (UTC) Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id B61205F640 for ; Thu, 10 Mar 2016 17:39:31 +0000 (UTC) Received: by mail-wm0-f45.google.com with SMTP id l68so40981234wml.0 for ; Thu, 10 Mar 2016 09:39:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=1RIB2J+2gT74Ej9Elj5DvEIdVLdgZ8HcBUnn9kUtuw0=; b=qXiyNlp9q60qTbO5PbkZpyesMpOiqZxqYVKEFEDnzkpUVepaj7NDkJAfWZZFEPtHxw UfJzaZXjOKci/toAP9KZFxSuBsterhz/J/SGvy8Rjz48AkUy2tPBKyrFCYIp4Ktkwc5w noChpbbZiOQM55gI74uYu7OmY5cJOZTGiz23cjEVwCbPl0RWaXHlUuLmsjvhyThUhbkU 7JgcrYKAL15z0X2ByNDhdeMUbj73q8Lj6hy38DhD71fZUEzcZA7ICox6tKqhyohPDplX v/8dkvgqp5nASvk8Ge9Z88n60p7/jGHK3AACEU5w6CcgUI2MjIH5Y+e2o9VIa3LS98jx pGEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=1RIB2J+2gT74Ej9Elj5DvEIdVLdgZ8HcBUnn9kUtuw0=; b=QX++h5z+QSV/K3PeIDFksqeueIzNRd9YL2nMOkhdkENxyx720C3v8h71KQqCbOHFWK NW30WRqL2WoXu59GmvTT99myNbkH2SuzEzS0AA04rah/4wVX6HwJgTVEmavHhxJHOPVb hfsLBRz0++8nx5/2e7i/mhAZ465PXRsglLUqD22w8OckyhPDVCMPzSLPkEwD3RT/YqNF QGJYucsXyt8MESWscdE5H/Kjn1oQ5e5Q+z6mR4zsL4j6CJcj/5Seez1P6nk1WrltGUx5 etk9ZMZHBU8njiDOldvhHd81vo6lu7bYhp63/9UwHC40nZkaGI9G/lg8SJ80XAPRcT3u bAgw== X-Gm-Message-State: AD7BkJJkHQjZuXsISt5m0lQ9nknGo2gbL8qqPhfCsS09hbaDJWvpPKf8ZXzOyTRuksyJ4w8llHlhVidROT/+9w== X-Received: by 10.28.68.85 with SMTP id r82mr5077541wma.65.1457631570554; Thu, 10 Mar 2016 09:39:30 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?B?RW3Eq2xzIMWgb2xtYW5pcw==?= Date: Thu, 10 Mar 2016 17:39:21 +0000 Message-ID: Subject: Re: Exception about too long clustering key To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a1148bcf0f9f784052db54b82 --001a1148bcf0f9f784052db54b82 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 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=C4=ABls =C5=A0olmanis wrote: > Hey Alex, > > I did do a grep for that message in the driver code base and it seems lik= e > 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 65= K > 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, wrote: > >> Hi Em=C4=ABls, >> >> 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=C4=ABls =C5=A0olmanis > > wrote: >> >>> Hello, >>> >>> I keep getting an exception about a clustering key being too long, like >>> >>> com.datastax.driver.core.exceptions.InvalidQueryException: The sum of a= ll 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(DefaultResult= SetFuture.java:179) >>> at com.datastax.driver.core.RequestHandler.setFinalResult(RequestHandl= er.java:184) >>> >>> >>> But the table has no clustering key. Even if I set the clustering key t= o >>> 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 >> >> --001a1148bcf0f9f784052db54b82 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
In case someone stumbles upon this same thing later.
<= br>
Ended up being a collection item that was too big (i.e., larg= er 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 messa= ge could definitely be better though, and I'll raise it with the devs.<= /div>

Regards,
Emils

On Wed, 9 Mar 2016 at 20:31 Em=C4=ABls = =C5=A0olmanis <emils.solmani= s@gmail.com> wrote:
Hey Alex,

I did do a grep for that message in the driver code b= ase and it seems like it's not there, so I think this is coming from th= e 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 2= 0:02 Alex Popescu, <alexp@datastax.com> wrote:
Hi=C2=A0Em=C4=ABls,

Directing this q= uestion to the Java driver mailing list will give you better chances to get= an answer:=C2=A0https://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=C4=ABls =C5=A0olmanis <emils.solmanis@gmail.com> wrote:
Hello,

I keep getting an exce= ption about a clustering key being too long, like
com.datastax.driver.core.exceptions.Inv=
alidQueryException: The sum of all clustering columns is too long (72650 &g=
t; 65535)
	at com.datastax.driver.core.Responses$Error.asException(Responses.java:136=
)
	at com.datastax.driver.core.DefaultResultSetFuture.onSet(DefaultResultSetF=
uture.java:179)
	at com.datastax.driver.core.RequestHandler.setFinalResult(RequestHandler.j=
ava:184)

But the table has no clustering key. Even i= f 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.=C2=A0

The only result Google gave me suggested this was about the cluste= ring key names, so I renamed all the fields in the schema def to 1-3 letter= s, to no avail.

Does anyone know what this is abou= t and how I can solve this?

Running Cassandra 2.2.= 4, Datastax driver 3.0.0.

Regards,
Emils=



--
Bests,

Alex Popescu |=C2=A0@al3xandr= u
Sen. Product Manager @ DataStax

--001a1148bcf0f9f784052db54b82--