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 jens.rantil@tink.se designates
 209.85.219.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACiwiCb4goC9R4JxgDJSE2L=fiHGvzZ_8GQMY8MosqrZim_skg@mail.gmail.com>
References: 
 <CACiwiCb4goC9R4JxgDJSE2L=fiHGvzZ_8GQMY8MosqrZim_skg@mail.gmail.com>
From: Jens Rantil <jens.rantil@tink.se>
Date: Tue, 1 Jul 2014 12:03:27 +0200
Message-ID: 
 <CAL+ArfVf6J=wmPiQQceVU7NgaTkhpQ0duMqvWjj2qBQXM=G-1Q@mail.gmail.com>
Subject: Re: Primary key question
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=089e01294b1053e05a04fd1ee499

--089e01294b1053e05a04fd1ee499
Content-Type: text/plain; charset=UTF-8

Hi again,

As a follow-up; if you have many `message_source_id`s you could also do:

CREATE TABLE integration_time (
message_source_id uuid,
traffic_data_type varchar,
integration_period varchar,
integration_time timestamp,
PRIMARY KEY (message_source_id,traffic_data_type,integration_period)
);

This might enable you to easier be able to query all traffic_data_types and
integration_periods for a single message_source_id without having to do a
heavy query across all of your cluster. You'll have the same uniqueness
property but this might, depending on your application, make things more
debuggable. The flip side is that your cluster could be slightly more
unbalanced if each message_source_id has a varied number of
`integration_time`s.

Just an idea,
Jens


On Tue, Jul 1, 2014 at 8:37 AM, Wim Deblauwe <wim.deblauwe@gmail.com> wrote:

> Hi,
>
> I have the following table:
>
> CREATE TABLE integration_time (
> message_source_id uuid,
> traffic_data_type varchar,
> integration_period varchar,
> integration_time timestamp,
> PRIMARY KEY ((message_source_id,traffic_data_type,integration_period))
> );
>
> I want the combination of (message_source_id, traffic_data_type,
> integration_period) to be unique. Is this the correct way to do it (with
> the double brackets) ?
>
> This table will be relative small, it just stores the last time something
> was done in the application for that unique combination of those 3
> parameters. Worst case there will be 30000 rows in that table and they will
> always be fetched by quering on the 3 parameters at the same time.
>
> regards,
>
> Wim
>

--089e01294b1053e05a04fd1ee499
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi again,<div><br></div><div>As a follow-up; if you have m=
any `message_source_id`s you could also do:</div><div><br></div><div><div s=
tyle=3D"font-family:arial,sans-serif;font-size:13px">CREATE TABLE integrati=
on_time (</div>

<div style=3D"font-family:arial,sans-serif;font-size:13px">message_source_i=
d uuid,</div><div style=3D"font-family:arial,sans-serif;font-size:13px">tra=
ffic_data_type varchar,</div><div style=3D"font-family:arial,sans-serif;fon=
t-size:13px">

integration_period varchar,</div><div style=3D"font-family:arial,sans-serif=
;font-size:13px">integration_time timestamp,</div><div style=3D"font-family=
:arial,sans-serif;font-size:13px">PRIMARY KEY (message_source_id,traffic_da=
ta_type,integration_period)</div>

<div style=3D"font-family:arial,sans-serif;font-size:13px">);</div></div><d=
iv style=3D"font-family:arial,sans-serif;font-size:13px"><br></div><div sty=
le=3D"font-family:arial,sans-serif;font-size:13px">This might enable you to=
 easier be able to query all traffic_data_types and integration_periods for=
 a single message_source_id without having to do a heavy query across all o=
f your cluster. You&#39;ll have the same uniqueness property but this might=
, depending on your application, make things more debuggable. The flip side=
 is that your cluster could be slightly more unbalanced if each message_sou=
rce_id has a varied number of `integration_time`s.</div>

<div style=3D"font-family:arial,sans-serif;font-size:13px"><br></div><div s=
tyle=3D"font-family:arial,sans-serif;font-size:13px">Just an idea,<br>Jens<=
/div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On=
 Tue, Jul 1, 2014 at 8:37 AM, Wim Deblauwe <span dir=3D"ltr">&lt;<a href=3D=
"mailto:wim.deblauwe@gmail.com" target=3D"_blank">wim.deblauwe@gmail.com</a=
>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Hi,<div><br></div><div>I ha=
ve the following table:</div><div><br></div><div><div>CREATE TABLE integrat=
ion_time (</div>

<div>message_source_id uuid,</div><div>traffic_data_type varchar,</div><div=
>integration_period varchar,</div>
<div>integration_time timestamp,</div><div>PRIMARY KEY ((message_source_id,=
traffic_data_type,integration_period))</div><div>);</div></div><div><br></d=
iv><div>I want the combination of (message_source_id, traffic_data_type, in=
tegration_period) to be unique. Is this the correct way to do it (with the =
double brackets) ?</div>


<div><br></div><div>This table will be relative small, it just stores the l=
ast time something was done in the application for that unique combination =
of those 3 parameters. Worst case there will be 30000 rows in that table an=
d they will always be fetched by quering on the 3 parameters at the same ti=
me.</div>


<div><br></div><div>regards,</div><div><br></div><div>Wim</div></div>
</blockquote></div><br></div>

--089e01294b1053e05a04fd1ee499--