You can now use composite indexes in Azure Cosmos DB to optimize additional cases of the most common inefficient queries! Anytime you have a slow or high RU query, you should first consider whether the query can be optimized with a composite index.
This blog is the final part of a series of blogs where we’ll demystify commonly confused concepts for developers learning how to query data using Azure Cosmos DB. Today, we’ll walk through tips and tricks for querying arrays.
In this blog, we’ll cover how to add and remove indexes using the new indexing policy editor. We’ll also highlight the differences in best practices for indexing in Azure Cosmos DB’s API for MongoDB and native MongoDB.
This blog is part two of a series of three blogs where we’ll demystify commonly confused concepts for developers learning how to query in the SQL (core) API in Azure Cosmos DB. We’ll look at the difference between null and undefined values.
With our latest service update, you can now create wildcard indexes in accounts that use Azure Cosmos DB’s API for MongoDB. Wildcard indexes are a popular feature in MongoDB 4.2 that allow you to index many properties without enumerating each one.
Azure Cosmos DB now supports case-insensitive Contains, StartsWith, EndsWith, and StringEquals. Additionally, both Contains and EndsWith have had significant performance improvements. You can now store string data in Azure Cosmos DB without having to worry about matching the case in the query.