Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
MIME-Version: 1.0
From: Philip Persad <philip.persad@gmail.com>
Date: Thu, 6 Oct 2016 09:30:57 -0700
Message-ID: <-8573435116428556423@unknownmsgid>
Subject: RE: Partition Key - Wide rows?
To: Ali Akhtar <ali.rac200@gmail.com>,
	"user@cassandra.apache.org" <user@cassandra.apache.org>
Content-Type: multipart/alternative; boundary=94eb2c03116c87ffb4053e34d15f
archived-at: Thu, 06 Oct 2016 16:31:10 -0000

--94eb2c03116c87ffb4053e34d15f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

1) No.  Your first 3 queries will work but not the last one (get issue by
id).  In Cassandra when you query you must include every preceding portion
of the primary key.

2) 64 bytes (16 * 4), or somewhat more if storing as strings?  I don't
think that's something I'd worry too much about.

3) Depends on how you build your partition key.  If partition key is (org
id), then you get one partition per org (probably bad depending on your
dataset).  If partition key is (org id, team id, project id) then you will
have one partition per project which is probably fine ( again, depending on
your dataset).

Cheers,

-Phil
------------------------------
From: Ali Akhtar <ali.rac200@gmail.com>
Sent: =E2=80=8E2016-=E2=80=8E10-=E2=80=8E06 9:04 AM
To: user@cassandra.apache.org
Subject: Partition Key - Wide rows?

Heya,

I'm designing some tables, where data needs to be stored in the following
hierarchy:

Organization -> Team -> Project -> Issues

I need to be able to retrieve issues:

- For the whole org - using org id
- For a team (org id + team id)
- For a project (org id + team id + project id)
- If possible, by using just the issue id

I'm considering using all 4 ids as the primary key. The first 3 will use
UUIDs, except issue id which will be an alphanumeric string, unique per
project.

1) Will this setup allow using all 4 query scenarios?
2) Will this make the primary key really long, 3 UUIDs + similar length'd
issue id?
3) Will this store issues as skinny rows, or wide rows? If an org has a lot
of teams, which have a lot of projects, which have a lot of issues, etc,
could I have issues w/ running out of the column limit of wide rows?
4) Is there a better way of achieving this scenario?

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

<html><head>
<meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Type"></=
head>
<body>
<div>
<div style=3D"FONT-SIZE:11pt;FONT-FAMILY:Calibri,sans-serif"><br><br>1) No.=
=C2=A0 Your first 3 queries will work but not the last one (get issue by id=
).=C2=A0 In Cassandra when you query you must include every preceding porti=
on of the primary key.<br><br>2) 64 bytes (16 * 4), or somewhat more if sto=
ring as strings?=C2=A0 I don&#39;t think that&#39;s something I&#39;d worry=
 too much about.<br><br>3) Depends on how you build your partition key.=C2=
=A0 If partition key is (org id), then you get one partition per org (proba=
bly bad depending on your dataset).=C2=A0 If partition key is (org id, team=
 id, project id) then you will have one partition per project which is prob=
ably fine ( again, depending on your dataset).<br><br>Cheers,<br><br>-Phil<=
/div></div>
<div dir=3D"ltr">
<hr>
<span style=3D"FONT-SIZE:11pt;FONT-FAMILY:Calibri,sans-serif;FONT-WEIGHT:bo=
ld">From: </span><span style=3D"FONT-SIZE:11pt;FONT-FAMILY:Calibri,sans-ser=
if"><a href=3D"mailto:ali.rac200@gmail.com">Ali Akhtar</a></span><br><span =
style=3D"FONT-SIZE:11pt;FONT-FAMILY:Calibri,sans-serif;FONT-WEIGHT:bold">Se=
nt: </span><span style=3D"FONT-SIZE:11pt;FONT-FAMILY:Calibri,sans-serif">=
=E2=80=8E2016-=E2=80=8E10-=E2=80=8E06 9:04 AM</span><br><span style=3D"FONT=
-SIZE:11pt;FONT-FAMILY:Calibri,sans-serif;FONT-WEIGHT:bold">To: </span><spa=
n style=3D"FONT-SIZE:11pt;FONT-FAMILY:Calibri,sans-serif"><a href=3D"mailto=
:user@cassandra.apache.org">user@cassandra.apache.org</a></span><br><span s=
tyle=3D"FONT-SIZE:11pt;FONT-FAMILY:Calibri,sans-serif;FONT-WEIGHT:bold">Sub=
ject: </span><span style=3D"FONT-SIZE:11pt;FONT-FAMILY:Calibri,sans-serif">=
Partition Key - Wide rows?</span><br><br></div></body></html><div dir=3D"lt=
r">Heya,<div><br></div><div>I&#39;m designing some tables, where data needs=
 to be stored in the following hierarchy:</div><div><br></div><div>Organiza=
tion -&gt; Team -&gt; Project -&gt; Issues</div><div><br></div><div>I need =
to be able to retrieve issues:</div><div><br></div><div>- For the whole org=
 - using org id</div><div>- For a team (org id + team id)</div><div>- For a=
 project (org id + team id + project id)</div><div>- If possible, by using =
just the issue id</div><div><br></div><div>I&#39;m considering using all 4 =
ids as the primary key. The first 3 will use UUIDs, except issue id which w=
ill be an alphanumeric string, unique per project.</div><div><br></div><div=
>1) Will this setup allow using all 4 query scenarios?</div><div>2) Will th=
is make the primary key really long, 3 UUIDs + similar length&#39;d issue i=
d?</div><div>3) Will this store issues as skinny rows, or wide rows? If an =
org has a lot of teams, which have a lot of projects, which have a lot of i=
ssues, etc, could I have issues w/ running out of the column limit of wide =
rows?</div><div>4) Is there a better way of achieving this scenario?</div><=
div><br></div><div><br></div><div><br></div><div><br></div></div>

--94eb2c03116c87ffb4053e34d15f--