Question

A data engineering team must perform a one-time bulk migration of 500 million documents into a new Cosmos DB container. During the load, no queries will run against the container; queries only begin after the migration completes and is validated. The team wants to minimize the RU cost and maximize write throughput during the bulk load, while still supporting rich queries afterward. What is the most effective indexing approach?

Accepted Answer

Set the indexing mode to 'none' during the bulk load, then switch to 'consistent' mode after the load to trigger a background reindex.

Answer

Keep the default 'consistent' indexing policy with all paths indexed throughout the migration.

Answer

Use 'lazy' indexing mode during the bulk load and leave it as 'lazy' permanently for lowest write cost.

Answer

Exclude all paths except '/id' using an includedPaths/excludedPaths policy and keep it that way permanently.