Become a super modeler


Published on

Slides from my webinar May 16, 2013.

Published in: Technology
1 Comment
  • Just a short question for my understanding: Why don't you use an index created by CREATE INDEX instead of creating own tables (like tag_index on slide 18)?
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Become a super modeler

  1. 1. Become a super modelerPatrick McFadin @PatrickMcFadinSenior Solutions ArchitectDataStaxThursday, May 16, 13
  2. 2. Become a super modelerPatrick McFadin @PatrickMcFadinSenior Solutions ArchitectDataStaxThursday, May 16, 13
  3. 3. ... the saga continues.This is the second part of a data modeling seriesPart 1:The data model is dead, long live the data model!• Relational -> Cassandra topics• Basic entity modeling• one-to-many• many-to-many•Transaction like modelingThursday, May 16, 13
  4. 4. Becoming a super modeler• Data model is the key to happiness• Successful deployments depend on it• Not just a Cassandra problem...3Thursday, May 16, 13
  5. 5. Time series - BasicCREATE TABLE temperature (weatherstation_id text,event_time timestamp,temperature text,PRIMARY KEY (weatherstation_id,event_time));• Weather station collects regular temperature• Each weather station is a row• Each event is a new column in a wide rowThursday, May 16, 13
  6. 6. Time series - Super!• Every second? Row would be too big• Order by access pattern• Partition the rows by day- One weather station by day5CREATE TABLE temperature_by_day (weatherstation_id text,date text,event_time timestamp,temperature text,PRIMARY KEY ((weatherstation_id,date),event_time)) WITH CLUSTERING ORDER BY (event_time DESC);Compound row keyReverse sort: Last event, first on rowThursday, May 16, 13
  7. 7. User model - basic• Plain ole entity table• One primary key• Booooring6CREATE TABLE users (username text PRIMARY KEY,first_name text,last_name text,address1 text,city text,postal_code text,last_login timestamp);Thursday, May 16, 13
  8. 8. Cassandra feature - Collections• Collections give you three types:- Set- List- Map• Each allow for dynamic updates• Fully supported in CQL 3• Requires serialization so don’t go crazy7CREATE TABLE collections_example (! id int PRIMARY KEY,! set_example set<text>,! list_example list<text>,! map_example map<int,text>);Thursday, May 16, 13
  9. 9. Cassandra Collections - Set• Set is sorted by CQL type comparator8INSERT INTO collections_example (id, set_example)VALUES(1, {1-one, 2-two});set_example set<text>Collection name Collection type CQLTypeThursday, May 16, 13
  10. 10. Cassandra Collections - Set Operations9UPDATE collections_exampleSET set_example = set_example + {3-three} WHERE id = 1;UPDATE collections_exampleSET set_example = set_example + {0-zero} WHERE id = 1;UPDATE collections_exampleSET set_example = set_example - {3-three} WHERE id = 1;• Adding an element to the set• After adding this element, it will sort to the beginning.• Removing an element from the setThursday, May 16, 13
  11. 11. Cassandra Collections - List• Ordered by insertion10list_example list<text>Collection name Collection type CQLTypeINSERT INTO collections_example (id, list_example)VALUES(1, [1-one, 2-two]);Thursday, May 16, 13
  12. 12. Cassandra Collections - List Operations• Adding an element to the end of a list11UPDATE collections_exampleSET list_example = list_example + [3-three] WHERE id = 1;UPDATE collections_exampleSET list_example = [0-zero] + list_example WHERE id = 1;• Adding an element to the beginning of a listUPDATE collections_exampleSET list_example = list_example - [3-three] WHERE id = 1;• Deleting an element from a listThursday, May 16, 13
  13. 13. Cassandra Collections - Map• Key and value• Key is sorted by CQL type comparator12INSERT INTO collections_example (id, map_example)VALUES(1, { 1 : one, 2 : two });map_example map<int,text>Collection name Collection type Value CQLTypeKey CQLTypeThursday, May 16, 13
  14. 14. Cassandra Collections - Map Operations• Add an element to the map13UPDATE collections_exampleSET map_example[3] = three WHERE id = 1;UPDATE collections_exampleSET map_example[3] = tres WHERE id = 1;DELETE map_example[3]FROM collections_example WHERE id = 1;• Update an existing element in the map• Delete an element in the mapThursday, May 16, 13
  15. 15. User model - Super!•Take boring user table and kick it up• Great for static + some dynamic•Takes advantage of row level isolation14CREATE TABLE user_with_location (! username text PRIMARY KEY,! first_name text,! last_name text,! address1 text,! city text,! postal_code text,! last_login timestamp,! location_by_date map<timeuuid,text>);Thursday, May 16, 13
  16. 16. Super user profile - Operations• Adding new login locations to the map15UPDATE user_with_locationSET last_login = now(), location_by_date = {now() :}WHERE username=PatrickMcFadin;UPDATE user_with_locationUSING TTL 2592000 // 30 DaysSET last_login = now(), location_by_date = {now() :}WHERE username=PatrickMcFadin;• Adding new login locations to the map +TTL!Thursday, May 16, 13
  17. 17. Indexing• Indexing expresses application intent• Fast access to specific queries• Secondary indexes != relational indexes• Use information you have. No pre-reads.16Goals:1. Create row key for speed2. Use wide rows for efficiencyThursday, May 16, 13
  18. 18. Keyword index• Use a word as a key• Columns are the occurrence• Ex: Index of tag words about videos17CREATE TABLE tag_index (tag varchar,videoid uuid,timestamp timestamp,PRIMARY KEY (tag, videoid));VideoId1 .. VideoIdNtagFastEfficientThursday, May 16, 13
  19. 19. Partial word index• Where row size will be large•Take one part for key, rest for columns name18CREATE TABLE email_index (domain varchar,user varchar,username varchar,PRIMARY KEY (domain, user));INSERT INTO email_index (domain, user, username)VALUES (,tcodd, tcodd);User: tcodd Email: tcodd@relational.comThursday, May 16, 13
  20. 20. Partial word index - Super!• Create partitions + partial indexes FTW19CREATE TABLE product_index (store int,part_number0_3 int,part_number4_9 int,count int,PRIMARY KEY ((store,part_number0_3), part_number4_9));INSERT INTO product_index (store,part_number0_3,part_number4_9,count)VALUES (8675309,7079,48575,3);SELECT countFROM product_indexWHERE store = 8675309AND part_number0_3 = 7079AND part_number4_9 = 48575;Compound row key!Fast and efficient!• Store #8675309 has 3 of part# 7079748575Thursday, May 16, 13
  21. 21. Bit map index• Multiple parts to a key• Create a truth table of the different combinations• Inserts == the number of combinations- 3 fields? 7 options (Not going to use null choice)- 4 fields? 15 options20Thursday, May 16, 13
  22. 22. Bit map index• Find a car in a lot by variable combinations21Make Model Color Combinationx Colorx Modelx x Model+Colorx Makex x Make+Colorx x Make+Modelx x x Make+Model+ColorThursday, May 16, 13
  23. 23. Bit map index -Table create• Make a table with three different key combos22CREATE TABLE car_location_index (make varchar,model varchar,color varchar,vehical_id int,lot_id int,PRIMARY KEY ((make,model,color),vehical_id));Compound row key with three different optionsThursday, May 16, 13
  24. 24. Bit map index - Adding records• Pre-optimize for 7 possible questions on insert23INSERT INTO car_location_index (make,model,color,vehical_id,lot_id)VALUES (Ford,Mustang,Blue,1234,8675309);INSERT INTO car_location_index (make,model,color,vehical_id,lot_id)VALUES (Ford,Mustang,,1234,8675309);INSERT INTO car_location_index (make,model,color,vehical_id,lot_id)VALUES (Ford,,Blue,1234,8675309);INSERT INTO car_location_index (make,model,color,vehical_id,lot_id)VALUES (Ford,,,1234,8675309);INSERT INTO car_location_index (make,model,color,vehical_id,lot_id)VALUES (,Mustang,Blue,1234,8675309);INSERT INTO car_location_index (make,model,color,vehical_id,lot_id)VALUES (,Mustang,,1234,8675309);INSERT INTO car_location_index (make,model,color,vehical_id,lot_id)VALUES (,,Blue,1234,8675309);Thursday, May 16, 13
  25. 25. Bit map index - Selecting records• Different combinations now possible24SELECT vehical_id,lot_idFROM car_location_indexWHERE make = FordAND model = AND color = Blue;vehical_id | lot_id------------+---------1234 | 8675309SELECT vehical_id,lot_idFROM car_location_indexWHERE make = AND model = AND color = Blue;vehical_id | lot_id------------+---------1234 | 86753098765 | 5551212Thursday, May 16, 13
  26. 26. Feeling super yet?• Use these skills. Save you they will.• Don’t settle for boring data models• Stay tuned for more!25• Final will be at the Cassandra Summit: June 11thThe worlds next top data modelThursday, May 16, 13
  27. 27. Be there!!!26Sony, eBay, Netflix, Intuit, Spotify... the list goes on. Don’t miss it.Here is my discount code! Use it: PMcVIPThursday, May 16, 13
  28. 28. Bonus!• DataStax Java Driver Preso - June 12th• Download today!27, May 16, 13
  29. 29. ThankYouQ&AThursday, May 16, 13