StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12820679
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-10-10T13:35:54.273
FavoriteCount
0
LastActivityDate
2012-10-10T13:35:54.273
LastEditDate
LastEditorUserId
0
OwnerUserId
1365913
ParentId
12808836
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Depending on the granularity you need in your queries (and the variability of that granularity), one way to handle this would be to slice up your map into a grid, where all your locations belong inside a grid square with a defined lat/lon bounding box. You can then do your initial query for grid square IDs, followed by locations inside those squares, with a representation something like this: <pre><code>GridSquareLat { key: [very_coarse_lat_value] { [square_lat_boundary]:[GridSquareIDList] [square_lat_boundary]:[GridSquareIDList] } ... } GridSquareLon { key: [very_coarse_lon_value] { [square_lon_boundary]:[GridSquareIDList] [square_lon_boundary]:[GridSquareIDList] } ... } Location { key: [locationID] { GridSquareID: [GridSquareID] <-- put a secondary index on this col Lat: [exact_lat] Lon: [exact_lon] ... } ... } </code></pre> You can then give Cassandra the GridSquareLat/Lon keys representing the very coarse grain lat/lon values, along with a column slice range that will reduce the columns returned to only those squares within your boundaries. You'll get two lists, one of grid square IDs for lat and one for lon. The intersection of these lists will be the grid squares in your range. To get the locations in these squares, query the Location CF, filtering on GridSquareID (using a secondary index, which will be efficient as long as your total grid square count is reasonable). You now have a reasonably sized list of locations with only a few very efficient queries, and you can easily reduce them to your exact list inside your application.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow can I efficiently make range query on two columns in cassandra?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USrs_atl
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow can I efficiently make range query on two columns in cassandra?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COI used something simillar. It's not exactly what I wanted but is ok
 singulars
 PostPostId
 PO
 UserUserId
 USd.as

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.