StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13727713
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-12-05T16:23:08.467
FavoriteCount
0
LastActivityDate
2012-12-05T16:34:12.900
LastEditDate
2012-12-05T16:34:12.900
LastEditorUserId
1274818
OwnerUserId
1274818
ParentId
13700288
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Denormalize! You must model your schema in a manner that will enable the types of queries you wish to perform. We create a reverse (aka inverted, inverse) index for such scenarios. <pre><code>CREATE TABLE report( KEY uuid PRIMARY KEY, svc1 bigint, svc2 bigint, svc3 bigint ); CREATE TABLE ReportsByTime( KEY ascii PRIMARY KEY ) with default_validation=uuid AND comparator=uuid; CREATE TABLE ReportsByUser( KEY bigint PRIMARY KEY )with default_validation=uuid AND comparator=uuid; </code></pre> See <a href="http://www.royans.net/arch/cassandra-inverted-index/" rel="nofollow">here</a> for a nice explanation. What you are doing now is generating your own <code>ascii</code> key in the <code>times</code> table, to enable yourself to perform the range slice query you want - it doesn't have to be <code>ascii</code> though just something you can use to programmatically generate your own slice keys with. You can use this approach to facilitate all of your queries, this likely isn't going to suit your application directly but the idea is the same. You can squeeze more out of this by adding meaningful values to the column keys of each table above. <pre><code>cqlsh:tester> select * from report; KEY | svc1 | svc2 | svc3 --------------------------------------+------+------+------ 1381b530-1dd2-11b2-0000-242d50cf1fb5 | 332 | 333 | 334 13818e20-1dd2-11b2-0000-242d50cf1fb5 | 222 | 223 | 224 13816710-1dd2-11b2-0000-242d50cf1fb5 | 112 | 113 | 114 cqlsh:tester> select * from times; KEY,1212051037 | 13818e20-1dd2-11b2-0000-242d50cf1fb5,13818e20-1dd2-11b2-0000-242d50cf1fb5 | 1381b530-1dd2-11b2-0000-242d50cf1fb5,1381b530-1dd2-11b2-0000-242d50cf1fb5 KEY,1212051035 | 13816710-1dd2-11b2-0000-242d50cf1fb5,13816710-1dd2-11b2-0000-242d50cf1fb5 | 13818e20-1dd2-11b2-0000-242d50cf1fb5,13818e20-1dd2-11b2-0000-242d50cf1fb5 KEY,1212051036 | 13818e20-1dd2-11b2-0000-242d50cf1fb5,13818e20-1dd2-11b2-0000-242d50cf1fb5 cqlsh:tester> select * from users; KEY | 13816710-1dd2-11b2-0000-242d50cf1fb5 | 13818e20-1dd2-11b2-0000-242d50cf1fb5 -------------+--------------------------------------+-------------------------------------- 23123123231 | 13816710-1dd2-11b2-0000-242d50cf1fb5 | 13818e20-1dd2-11b2-0000-242d50cf1fb5 </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POTimestamp / date as key for cassandra column family / hector
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. UStysonjh
UserOwnerUserId
1. UStysonjh
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.