Firestore queries and indexes in GCP - Step-by-Step Execution

Process Flow - Firestore queries and indexes

Start Query

↓

Check Query Filters

↓

Determine Index Needed

↓

Is Index Available?

No→Create Index

↓

Wait for Index Build

↓

Execute Query Using Index

↓

Return Results

↓

End

This flow shows how Firestore processes a query by checking filters, determining if an index is needed, creating it if missing, then executing the query using the index to return results.

Execution Sample

GCP

db.collection('users')
  .where('age', '>=', 18)
  .where('city', '==', 'NYC')
  .orderBy('age')
  .get()

This query fetches users aged 18 or older living in NYC, ordered by age.

Process Table

Step	Action	Query Filters	Index Needed	Index Exists	Result
1	Start query execution	age >= 18, city == 'NYC', orderBy age	Composite index on age and city	Check index availability	Pending
2	Index check	age >= 18, city == 'NYC', orderBy age	Composite index on age and city	No	Trigger index creation
3	Create index	age >= 18, city == 'NYC', orderBy age	Composite index on age and city	Building	Wait for index build
4	Index build complete	age >= 18, city == 'NYC', orderBy age	Composite index on age and city	Yes	Proceed to query
5	Execute query	age >= 18, city == 'NYC', orderBy age	Composite index on age and city	Yes	Return matching documents
6	End				Query complete with results

💡 Query ends after index is available and results are returned.

Status Tracker

Variable	Start	After Step 2	After Step 4	Final
IndexExists	Unknown	No	Yes	Yes
QueryResult	Empty	Empty	Empty	Documents matching filters

Key Moments - 3 Insights

Why does Firestore sometimes ask to create a new index before running a query?

Because the query uses multiple filters or ordering that require a composite index not yet created, as shown in execution_table step 2 where index existence is checked and found missing.

What happens if the required index is still building when you run the query?

The query waits until the index build completes before returning results, as shown in execution_table step 3 where it waits for the index to build.

Can a query run without an index in Firestore?

Simple queries with single filters or no ordering can run without indexes, but complex queries with multiple filters or orderBy need indexes, as shown by the index check in execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does Firestore decide to create a new index?

A Step 1

B Step 4

C Step 2

D Step 5

💡 Hint

Check the 'Index Exists' and 'Action' columns in execution_table row for step 2.

According to variable_tracker, what is the value of IndexExists after step 4?

A No

B Yes

C Unknown

D Building

💡 Hint

Look at the 'IndexExists' row under 'After Step 4' in variable_tracker.

If the query had only one filter without ordering, how would the execution_table change?

A It would skip index creation steps

B It would add more index creation steps

C It would wait longer for index build

D It would fail immediately

💡 Hint

Consider how simple queries behave regarding indexes as explained in key_moments.

Concept Snapshot

Firestore queries use filters and ordering.
Complex queries need composite indexes.
If index missing, Firestore creates it.
Query waits for index build before returning results.
Simple queries may not need indexes.

Full Transcript

This visual execution traces how Firestore handles queries and indexes. When a query with filters and ordering runs, Firestore checks if a composite index exists. If not, it triggers index creation and waits for it to build. Once ready, the query executes using the index and returns matching documents. Variables track index existence and query results. Key moments clarify why indexes are needed and what happens during index building. The quiz tests understanding of index creation steps and variable states.