Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of rcoli@eventbrite.com designates
 209.85.216.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAEo-6+S9J7rTc4Ko+tzfiuYDRW+LLyixEF7q0CBow45LTdQOpQ@mail.gmail.com>
References: 
 <CALemSr51sPiFJy+qpmPJLSgnTmtWznYM_O0OCynhK1B3KvtZbQ@mail.gmail.com>
	<CAEDUwd2TFo3_Wy+AtUhJzTpidbH28G5S1yZ_9rvxVfmYtbiqnA@mail.gmail.com>
	<CAEo-6+S9J7rTc4Ko+tzfiuYDRW+LLyixEF7q0CBow45LTdQOpQ@mail.gmail.com>
Date: Thu, 1 Aug 2013 17:32:08 -0700
Message-ID: 
 <CAEDUwd2qO-2Y84jLVKA-QFQBcJnsL7b8RL-_q11brO-SZszXFA@mail.gmail.com>
Subject: Re: Secondary Indexes On Partitioned Time Series Data Question
From: Robert Coli <rcoli@eventbrite.com>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Content-Type: multipart/alternative; boundary=089e0158b112b8352404e2ec16d3

--089e0158b112b8352404e2ec16d3
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Aug 1, 2013 at 2:34 PM, Shahab Yunus <shahab.yunus@gmail.com> wrote:

> Can you shed some more light (or point towards some other resource) that
> why you think built-in Secondary Indexes should not be used easily or
> without much consideration? Thanks.
>

1) Secondary indexes are more or less modeled like a manual pseudo
Secondary Index CF would be.
2) Except they are more opaque than doing it yourself. For example you
cannot see information on them in nodetool cfstats.
3) And there have been a steady trickle of bugs which relate to their
implementation, in many cases resulting in them not returning the data they
should. [1]
4) These bugs would not apply to a manual pseudo Secondary Index CF.
5) And the only benefits you get are the marginal convenience of querying
the secondary index instead of a second CF, and atomic synchronized update.
6) Which most people do not actually need.

tl;dr : "unless you need the atomic update property, just use a manual
pseudo secondary index CF"

=Rob

[1] https://issues.apache.org/jira/browse/CASSANDRA-4785 ,
https://issues.apache.org/jira/browse/CASSANDRA-5540 ,
https://issues.apache.org/jira/browse/CASSANDRA-2897 , etc.

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

<div dir=3D"ltr">On Thu, Aug 1, 2013 at 2:34 PM, Shahab Yunus <span dir=3D"=
ltr">&lt;<a href=3D"mailto:shahab.yunus@gmail.com" target=3D"_blank">shahab=
.yunus@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div c=
lass=3D"gmail_quote">
<blockquote 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;p=
adding-left:1ex"><div dir=3D"ltr"><div>Can you shed some more light (or poi=
nt towards some other resource) that why you think built-in Secondary Index=
es should not be used easily or without much consideration? Thanks.</div>
</div></blockquote><div><br></div><div style>1) Secondary indexes are more =
or less modeled like a manual pseudo Secondary Index CF would be.</div><div=
 style>2) Except they are more opaque than doing it yourself. For example y=
ou cannot see information on them in nodetool cfstats.</div>
<div style>3) And there have been a steady trickle of bugs which relate to =
their implementation, in many cases resulting in them not returning the dat=
a they should. [1]</div><div style>4) These bugs would not apply to a manua=
l pseudo Secondary Index CF.</div>
<div style>5) And the only benefits you get are the marginal convenience of=
 querying the secondary index instead of a second CF, and atomic synchroniz=
ed update.</div><div style>6) Which most people do not actually need.</div>
<div style><br></div><div style>tl;dr : &quot;unless you need the atomic up=
date property, just use a manual pseudo secondary index CF&quot;</div><div =
style><br></div><div style>=3DRob</div><div style><br></div><div style>[1]=
=A0<a href=3D"https://issues.apache.org/jira/browse/CASSANDRA-4785">https:/=
/issues.apache.org/jira/browse/CASSANDRA-4785</a> ,=A0<a href=3D"https://is=
sues.apache.org/jira/browse/CASSANDRA-5540">https://issues.apache.org/jira/=
browse/CASSANDRA-5540</a> , <a href=3D"https://issues.apache.org/jira/brows=
e/CASSANDRA-2897">https://issues.apache.org/jira/browse/CASSANDRA-2897</a> =
, etc.</div>
<div style><br></div></div></div></div>

--089e0158b112b8352404e2ec16d3--