Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of petter.von.dolwitz@gmail.com
 designates 209.85.128.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAEDUwd08k2FwSP5m3qJfax2x6HsdMT8SYP-LvsRhYmtTZQac7A@mail.gmail.com>
References: 
 <CADFYdErMz1icXGZC3khG6SnOO5X+gviYTPacn87W90T4a9B6Vg@mail.gmail.com>
	<CAEDUwd08k2FwSP5m3qJfax2x6HsdMT8SYP-LvsRhYmtTZQac7A@mail.gmail.com>
Date: Sun, 8 Sep 2013 09:44:54 +0200
Message-ID: 
 <CADFYdEomH7safCzynhL3Y0z8jL03pyAV2LQ8jxEdxiStKNhxDg@mail.gmail.com>
Subject: Re: Cannot get secondary indexes on fields in compound primary key to
 work (Cassandra 2.0.0)
From: "Petter von Dolwitz (Hem)" <petter.von.dolwitz@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a113378d88f6f9504e5da72f1

--001a113378d88f6f9504e5da72f1
Content-Type: text/plain; charset=ISO-8859-1

Thank you for you reply.

I will look into this. I cannot not get my head around why the scenario I
am describing does not work though. Should I report an issue around this or
is this expected behaviour? A similar setup is described on this blog post
by the development lead.

http://www.datastax.com/dev/blog/cql3-for-cassandra-experts


2013/9/6 Robert Coli <rcoli@eventbrite.com>

> On Fri, Sep 6, 2013 at 6:18 AM, Petter von Dolwitz (Hem) <
> petter.von.dolwitz@gmail.com> wrote:
>
>> I am struggling with getting secondary indexes to work. I have created
>> secondary indexes on some fields that are part of the compound primary key
>> but only one of the indexes seems to work (the one set on the field 'e' on
>> the table definition below). Using any other secondary index in a where
>> clause causes the message "Request did not complete within rpc_timeout.".
>> It seems like if a put a value in the where clause that does not exist in a
>> column with secondary index then cassandra quickly return with the result
>> (0 rows) but if a put in a value that do exist I get a timeout. There is no
>> exception in the logs in connection with this. I've tried to increase the
>> timeout to a minute but it does not help.
>>
>
> In general unless you absolutely need the atomicity of the update of a
> secondary index with the underlying storage row, you are better off making
> a manual secondary index column family.
>
> =Rob
>

--001a113378d88f6f9504e5da72f1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thank you for you reply.<div><br></div><div>I will look in=
to this. I cannot not get my head around why the scenario I am describing d=
oes not work though. Should I report an issue around this or is this expect=
ed behaviour? A similar setup is described on this blog post by the develop=
ment lead.</div>
<div><br></div><div><a href=3D"http://www.datastax.com/dev/blog/cql3-for-ca=
ssandra-experts">http://www.datastax.com/dev/blog/cql3-for-cassandra-expert=
s</a></div><div><br></div><div><br><div class=3D"gmail_extra"><br><br><div =
class=3D"gmail_quote">
2013/9/6 Robert Coli <span dir=3D"ltr">&lt;<a href=3D"mailto:rcoli@eventbri=
te.com" target=3D"_blank">rcoli@eventbrite.com</a>&gt;</span><br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width=
:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-lef=
t:1ex">
<div dir=3D"ltr"><div class=3D"im">On Fri, Sep 6, 2013 at 6:18 AM, Petter v=
on Dolwitz (Hem) <span dir=3D"ltr">&lt;<a href=3D"mailto:petter.von.dolwitz=
@gmail.com" target=3D"_blank">petter.von.dolwitz@gmail.com</a>&gt;</span> w=
rote:<br>
</div><div class=3D"gmail_extra">
<div class=3D"gmail_quote"><div class=3D"im"><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-col=
or:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir=3D"l=
tr"><div>
I am struggling with getting secondary indexes to work. I have created seco=
ndary indexes on some fields that are part of the compound primary key but =
only one of the indexes seems to work (the one set on the field &#39;e&#39;=
 on the table definition below). Using any other secondary index in a where=
 clause causes the message &quot;Request did not complete within rpc_timeou=
t.&quot;. It seems like if a put a value in the where clause that does not =
exist in a column with secondary index then cassandra quickly return with t=
he result (0 rows) but if a put in a value that do exist I get a timeout. T=
here is no exception in the logs in connection with this. I&#39;ve tried to=
 increase the timeout to a minute but it does not help.<br>

</div></div></blockquote><div><br></div></div><div>In general unless you ab=
solutely need the atomicity of the update of a secondary index with the und=
erlying storage row, you are better off making a manual secondary index col=
umn family.</div>

<div><br></div><div>=3DRob=A0</div></div></div></div>
</blockquote></div><br></div></div></div>

--001a113378d88f6f9504e5da72f1--