Skip to content
Hallway
0:00 / 0:00

#cassandra#cql#datamodeling

C* Summit 2013: The World's Next Top Data Model

PlanetCassandra

6.1K subscribers • 2 videos on Hallway

YouTube
  • Recommended by 1 person: 1 on Stack Overflow and its sister sites.
  • Presented by Patrick McFadin, Principal Solutions Architect at DataStax
  • Linked in the descriptionSlides on SlideShare

Intermediate. Assumes working knowledge.

13K views13 years ago1 recommendation

Databases and dataSoftware designDatabase internalsNoSQL and document databasesSoftware architecture

Patrick McFadin explains how to design effective data models in Apache Cassandra by understanding its storage internals and indexing mechanisms.

Speaker: Patrick McFadin, Principal Solutions Architect at DataStax Slides: slideshare.net/planetcassandra/c-summit-2013-the-worlds-next… You know you need Cassandra for it's uptime and scaling, but what about that data model? Let's bridge that gap and get you building your game changing app. We'll break down topics like storing objects and indexing for fast retrieval. You will see by understanding a few things about Cassandra internals, you can put your data model in the spotlight. The goal of this talk is to get you comfortable working with data in Cassandra throughout the application lifecycle. What are you waiting for? The cameras are waiting!

Why it's here

1 person recommends this

What people say. Recommended as a helpful resource for understanding how to model data and handle queries without unsupported operations like NOT IN in Cassandra.

Zansonon Stack Overflow • Recommends

On “how to perform "not in" filter in cql3 query select?”

"not in" is not a supported operation in CQL. Cassandra at its heart is still based on key indexed rows. So that query is basically the same as "select * from users", as you have to go through every row and figure out if it does not match the in. If you want to do that type of query you will want to setup a map reduce job to perform it. When using Cassandra what you actually want to do is de-normalize your data model so that the queries you application performs end up querying a single partition (or just a few partitions) for their results. Also find some great webinars and talks on Cassandra data modeling link to this video link to this video link to this video
12View the answer