Skip to content

Commit 8bdf330

Browse files
committed
update wording for clarity
1 parent 43fc34e commit 8bdf330

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/cosmos-db/index-policy.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,9 @@ Any indexing policy has to include the root path `/*` as either an included or a
8787

8888
- If the indexing mode is set to **consistent**, the system properties `id` and `_ts` are automatically indexed.
8989

90-
- All explicitly included paths will have values added to the index for each item in the container, even if the path is undefined for a given item.
90+
- If an explicitly indexed path doesn't exist in an item, a value will be added to the index to indicate that the path is undefined.
91+
92+
All explicitly included paths will have values added to the index for each item in the container, even if the path is undefined for a given item.
9193

9294
See [this section](how-to-manage-indexing-policy.md#indexing-policy-examples) for indexing policy examples for including and excluding paths.
9395

@@ -129,7 +131,7 @@ Azure Cosmos DB, by default, won't create any spatial indexes. If you would like
129131

130132
Queries that have an `ORDER BY` clause with two or more properties require a composite index. You can also define a composite index to improve the performance of many equality and range queries. By default, no composite indexes are defined so you should [add composite indexes](how-to-manage-indexing-policy.md#composite-index) as needed.
131133

132-
Unlike with included or excluded paths, you can't create a path with the `/*` wildcard. Every composite path has an implicit `/?` at the end of the path that you don't need to specify. Composite paths lead to a scalar value that is the only value included in the composite index. Values for each path in every composite index defined on a container will be stored for all items, even if the path is undefined for a given item.
134+
Unlike with included or excluded paths, you can't create a path with the `/*` wildcard. Every composite path has an implicit `/?` at the end of the path that you don't need to specify. Composite paths lead to a scalar value that is the only value included in the composite index. If a path in a composite index doesn't exist in an item, a value will be added to the index to indicate that the path is undefined.
133135

134136
When defining a composite index, you specify:
135137

0 commit comments

Comments
 (0)