RECOMMENDED PATHS
ArchitectLOGIN TO START THIS PATH
VIEW COURSES
0%
DS220: DataStax Enterprise 6 Practical Application Data Modeling with Apache Cassandra™
0%
DS101: Introduction to Apache Cassandra™
0%
DS201: DataStax Enterprise 6 Foundations of Apache Cassandra™
0%
DS210: DataStax Enterprise 6 Operations with Apache Cassandra™
DeveloperLOGIN TO START THIS PATH
VIEW COURSES
0%
DS101: Introduction to Apache Cassandra™
0%
DS201: DataStax Enterprise 6 Foundations of Apache Cassandra™
0%
DS220: DataStax Enterprise 6 Practical Application Data Modeling with Apache Cassandra™
Graph SpecialistLOGIN TO START THIS PATH
VIEW COURSES
0%
DS101: Introduction to Apache Cassandra™
0%
DS201: DataStax Enterprise 6 Foundations of Apache Cassandra™
0%
DS220: DataStax Enterprise 6 Practical Application Data Modeling with Apache Cassandra™
0%
DS330: DataStax Enterprise 6 Graph
UNIT CONTENTS
Unit Status

Recommended Content

 
 
  Previous Unit: Mapping Conceptual To Logical Model
Finish & Next Unit: Physical Data Modeling  

DSE Version: 6.0

Logical Data Modeling

Video

Exercises

Now let's get into the details of creating a logical data model. In this unit, we go through some rules to consider when putting together your logical data model.

NO TRANSCRIPT AVAILABLE.

No write up.

Exercise 4.3: Extend The KillrVideo Logical Model

In this exercise, you will:

  • Add tables to the logical model to support additional queries
  • Ensure that the mapping rules are applied appropriately

Background

The KillrVideo product team wants to add additional query capabilities to the application. Specifically the following queries will need to be supported:

  • Q1. Find all user videos that match a specific tag (show the most recent uploaded videos first)
  • Q2. Find all movies that features a specific actor and release year range (show the most recent videos first, and then sorted by title)
  • Q3. Find all movies that features a specific actor, genre and release year range (show the most recent videos first, and then sorted by title)

The conceptual model outlines the available attributes for the appropriate entities and relationships.



Steps

  1. On paper or in a text editor, create a logical Chebotko diagram that can support Q1.
  2. On paper or in a text editor, create a logical Chebotko diagram that can support Q2.
  3. On paper or in a text editor, create a logical Chebotko diagram that can support Q3.
  4. For each query, answer the following questions:
    1. What entity or relationship type is being stored in a partition or row?
    2. What are the key attribute(s) for this table?
    3. What attribute is used for the partition key(s) that enabled the equality query?
    4. What attribute is used for the cluster column(s) that enables the inequality / range scan?
    5. What are the clustering column(s) and ordering that support the required results?
No FAQs.
No resources.
Comments are closed.