Why secondary indexes enable flexible queries in DynamoDB

Introduction

Secondary indexes let you search your data in new ways without changing your main table. They make your queries more flexible and faster.

You want to find items by a different attribute than the main key.

You need to sort or filter data using another column.

You want to run queries without scanning the whole table.

You want to improve performance for specific search patterns.

You want to keep your main table structure simple but still support many queries.

Syntax

DynamoDB

CREATE GLOBAL SECONDARY INDEX index_name ON table_name (partition_key, sort_key);

-- Or when creating a table:
CREATE TABLE table_name (
  primary_key_attribute TYPE,
  other_attribute TYPE,
  ...
) WITH GLOBAL SECONDARY INDEXES (
  index_name (partition_key_attribute, sort_key_attribute)
);

Secondary indexes can have their own partition and sort keys.

Global Secondary Indexes (GSI) allow querying by different keys than the main table.

Examples

This creates a table where the main key is Artist and SongTitle, but you can also query by AlbumTitle and Year using the AlbumIndex.

DynamoDB

CREATE TABLE Music (
  Artist STRING,
  SongTitle STRING,
  AlbumTitle STRING,
  Year INT,
  PRIMARY KEY (Artist, SongTitle)
) WITH GLOBAL SECONDARY INDEXES (
  AlbumIndex (AlbumTitle, Year)
);

This query uses the secondary index to find all songs in the album 'Greatest Hits' quickly.

DynamoDB

SELECT * FROM Music.AlbumIndex WHERE AlbumTitle = 'Greatest Hits';

Sample Program

This example creates a Books table with ISBN as the main key. It adds a secondary index on Author and Title so you can find all books by a specific author quickly.

DynamoDB

CREATE TABLE Books (
  ISBN STRING,
  Title STRING,
  Author STRING,
  Genre STRING,
  PRIMARY KEY (ISBN)
) WITH GLOBAL SECONDARY INDEXES (
  AuthorIndex (Author, Title)
);

-- Insert sample data
INSERT INTO Books VALUES ('123', 'Learn SQL', 'Alice', 'Education');
INSERT INTO Books VALUES ('456', 'Cooking 101', 'Bob', 'Cooking');
INSERT INTO Books VALUES ('789', 'Advanced SQL', 'Alice', 'Education');

-- Query by Author using secondary index
SELECT * FROM Books.AuthorIndex WHERE Author = 'Alice';

Important Notes

Secondary indexes increase storage and write costs because data is duplicated.

They help avoid slow full table scans by enabling targeted queries.

Remember to choose index keys based on your query needs.

Summary

Secondary indexes let you query data in new ways without changing the main table.

They improve query speed and flexibility by using different keys.

Use them to support multiple search patterns efficiently.

Practice

1. What is the main benefit of using secondary indexes in DynamoDB?

easy

A. They allow querying data using different keys without changing the main table

B. They automatically backup your data

C. They increase the storage capacity of the table

D. They encrypt data for security

Solution

1. Step 1: Understand the role of secondary indexes

   Secondary indexes let you query the table using keys other than the primary key.

2. Step 2: Compare other options

   Options A, B, and C describe features unrelated to secondary indexes.

3. Final Answer:

   They allow querying data using different keys without changing the main table -> Option A

4. Quick Check:

   Secondary indexes = flexible queries [OK]

Hint: Secondary indexes = new query keys without table changes [OK]

Common Mistakes:

• Confusing secondary indexes with backups
• Thinking indexes increase storage size
• Assuming indexes encrypt data

2. Which of the following is the correct syntax to create a Global Secondary Index (GSI) in a DynamoDB table definition?

easy

A. {"IndexName": "GSI1", "KeySchema": [{"AttributeName": "Category", "KeyType": "RANGE"}], "Projection": {"ProjectionType": "KEYS_ONLY"}}

B. {"IndexName": "GSI1", "KeySchema": [{"AttributeName": "Category", "KeyType": "HASH"}], "Projection": {"ProjectionType": "ALL"}}

C. {"IndexName": "GSI1", "KeySchema": [{"AttributeName": "Category", "KeyType": "PRIMARY"}], "Projection": {"ProjectionType": "ALL"}}

D. {"IndexName": "GSI1", "KeySchema": [{"AttributeName": "Category", "KeyType": "SORT"}], "Projection": {"ProjectionType": "INCLUDE"}}

Solution

1. Step 1: Identify correct KeyType for GSI partition key

   For a GSI, the partition key uses KeyType 'HASH'. {"IndexName": "GSI1", "KeySchema": [{"AttributeName": "Category", "KeyType": "HASH"}], "Projection": {"ProjectionType": "ALL"}} uses 'HASH'.

2. Step 2: Check Projection type

   {"IndexName": "GSI1", "KeySchema": [{"AttributeName": "Category", "KeyType": "HASH"}], "Projection": {"ProjectionType": "ALL"}} uses 'ALL', which is valid. Other options use invalid KeyTypes like 'PRIMARY' or 'SORT'.

3. Final Answer:

   {"IndexName": "GSI1", "KeySchema": [{"AttributeName": "Category", "KeyType": "HASH"}], "Projection": {"ProjectionType": "ALL"}} -> Option B

4. Quick Check:

   GSI partition key = HASH [OK]

Hint: GSI partition key must be 'HASH' not 'RANGE' or others [OK]

Common Mistakes:

• Using 'PRIMARY' or 'SORT' as KeyType
• Confusing partition key with sort key
• Wrong ProjectionType values

3. Given a DynamoDB table with a Global Secondary Index (GSI) on attribute Category, what will the following query return?

Query({
  TableName: 'Products',
  IndexName: 'CategoryIndex',
  KeyConditionExpression: 'Category = :cat',
  ExpressionAttributeValues: { ':cat': 'Books' }
})

medium

A. All items where the primary key equals 'Books'

B. All items in the table regardless of Category

C. An error because the query does not specify the primary key

D. All items where the Category attribute equals 'Books' using the GSI

Solution

1. Step 1: Understand the use of IndexName in the query

   Specifying IndexName means the query uses the GSI on 'Category'.

2. Step 2: Analyze KeyConditionExpression

   The query filters items where 'Category' equals 'Books' using the GSI.

3. Final Answer:

   All items where the Category attribute equals 'Books' using the GSI -> Option D

4. Quick Check:

   Query with GSI filters by Category = 'Books' [OK]

Hint: Query with IndexName uses that index's keys [OK]

Common Mistakes:

• Assuming query filters primary key without IndexName
• Expecting error without primary key in main table
• Thinking query returns all items

4. You tried to query a DynamoDB table using a secondary index but got an error: ValidationException: Query condition missed key schema element. What is the most likely cause?

medium

A. You forgot to create the secondary index before querying

B. You used the primary key instead of the secondary index name

C. You did not specify the partition key attribute of the secondary index in the query

D. You used a Scan operation instead of Query

Solution

1. Step 1: Understand the error message

   The error means the query is missing a required key attribute from the index's key schema.

2. Step 2: Identify the missing key

   When querying a secondary index, you must specify its partition key attribute in the KeyConditionExpression.

3. Final Answer:

   You did not specify the partition key attribute of the secondary index in the query -> Option C

4. Quick Check:

   Missing index partition key causes ValidationException [OK]

Hint: Always include index partition key in query condition [OK]

Common Mistakes:

• Using primary key attributes instead of index keys
• Querying before index creation
• Confusing Scan with Query operation

5. You have a DynamoDB table with a primary key on UserId and a Global Secondary Index (GSI) on Email. You want to efficiently find users by their email address. Which approach best uses the GSI to achieve this?

hard

A. Query the table using the GSI with KeyConditionExpression 'Email = :emailValue'

B. Scan the entire table filtering items where Email equals the value

C. Query the table using the primary key UserId with the email value

D. Create a new table with Email as the primary key

Solution

1. Step 1: Identify the best way to find users by Email

   The GSI on Email allows querying by Email efficiently without scanning.

2. Step 2: Compare options

   Query the table using the GSI with KeyConditionExpression 'Email = :emailValue' uses the GSI query correctly. Scan the entire table filtering items where Email equals the value scans, which is slow. Query the table using the primary key UserId with the email value uses UserId, which won't help find by Email. Create a new table with Email as the primary key is unnecessary duplication.

3. Final Answer:

   Query the table using the GSI with KeyConditionExpression 'Email = :emailValue' -> Option A

4. Quick Check:

   Use GSI query for efficient Email lookup [OK]

Hint: Use GSI query, not scan or primary key, for alternate keys [OK]

Common Mistakes:

• Using Scan instead of Query on GSI
• Querying primary key with wrong attribute
• Creating redundant tables instead of indexes