Skip to content

Commit 6ce120a

Browse files
authored
Merge pull request #174781 from timsander1/master
indexing metrics and distinct doc updates
2 parents 366be0a + 1a93565 commit 6ce120a

File tree

2 files changed

+6
-3
lines changed

2 files changed

+6
-3
lines changed

articles/cosmos-db/sql/index-metrics.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: timsander1
55
ms.service: cosmos-db
66
ms.subservice: cosmosdb-sql
77
ms.topic: conceptual
8-
ms.date: 09/24/2021
8+
ms.date: 10/05/2021
99
ms.author: tisande
1010
---
1111
# Indexing metrics in Azure Cosmos DB
@@ -88,6 +88,9 @@ The potential single indexes and utilized composite indexes respectively show th
8888

8989
Consider the list of potential indexed paths as recommendations rather than conclusive evidence that a query will use a specific indexed path. The potential indexed paths are not an exhaustive list of indexed paths that a query could use. Additionally, it's possible that some potential indexed paths won't have any impact on query performance. [Add the recommended indexed paths](how-to-manage-indexing-policy.md) and confirm that they improve query performance.
9090

91+
> [!NOTE]
92+
> Do you have any feedback about the indexing metrics? We want to hear it! Feel free to share feedback directly with the Azure Cosmos DB engineering team: [email protected]
93+
9194
## Index impact score
9295

9396
The index impact score is the likelihood that an indexed path, based on the query shape, has a significant impact on query performance. In other words, the index impact score is the probability that, without that specific indexed path, the query RU charge would have been substantially higher.

articles/cosmos-db/sql/sql-query-keywords.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: timsander1
55
ms.service: cosmos-db
66
ms.subservice: cosmosdb-sql
77
ms.topic: conceptual
8-
ms.date: 09/20/2021
8+
ms.date: 10/05/2021
99
ms.author: tisande
1010

1111
---
@@ -112,7 +112,7 @@ SELECT COUNT(1) FROM (SELECT DISTINCT f.lastName FROM f)
112112
|Node.js SDK|Unsupported|
113113
|Python SDK|Unsupported|
114114

115-
There are some additional restrictions on queries with an aggregate system function and a subquery with `DISTINCT`:
115+
There are some additional restrictions on queries with an aggregate system function and a subquery with `DISTINCT`. The below queries are unsupported:
116116

117117
|**Restriction**|**Example**|
118118
|-------|----------------------|

0 commit comments

Comments
 (0)