Skip to content

Commit 1de6e66

Browse files
authored
Merge pull request #252909 from seesharprun/cosmos-mongo-indexing
Cosmos DB | Move MongoDB indexing article to conceptual
2 parents 059853c + ebeb944 commit 1de6e66

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

articles/cosmos-db/mongodb/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -145,6 +145,8 @@
145145
- name: Azure Cosmos DB resource model
146146
displayName: collection, document
147147
href: ../resource-model.md
148+
- name: Indexing
149+
href: indexing.md
148150
- name: Partitioning (sharding)
149151
items:
150152
- name: Partitioning overview
@@ -357,8 +359,6 @@
357359
href: find-request-unit-charge.md
358360
- name: Change streams
359361
href: change-streams.md
360-
- name: Manage data indexing
361-
href: indexing.md
362362
- name: Time to live
363363
href: time-to-live.md
364364
- name: Use multi-document transactions

articles/cosmos-db/mongodb/indexing.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article presents an overview of Azure Cosmos DB indexing capab
44
ms.service: cosmos-db
55
ms.subservice: mongodb
66
ms.devlang: javascript
7-
ms.topic: how-to
7+
ms.topic: conceptual
88
ms.date: 12/2/2022
99
author: gahl-levy
1010
ms.author: gahllevy
@@ -284,13 +284,13 @@ In the preceding example, omitting the ```"university":1``` clause returns an er
284284
285285
Unique indexes need to be created while the collection is empty.
286286
287-
Unique indexes on nested fields are not supported by default due to limiations with arrays. If your nested field does not contain an array, the index will work as intended. If your nested field contains an array (anywhere on the path), that value will be ignored in the unique index and uniqueness wil not be preserved for that value.
287+
Unique indexes on nested fields are not supported by default due to limitations with arrays. If your nested field does not contain an array, the index will work as intended. If your nested field contains an array (anywhere on the path), that value will be ignored in the unique index and uniqueness will not be preserved for that value.
288288
289289
For example a unique index on people.tom.age will work in this case since there's no array on the path:
290290
```javascript
291291
{ "people": { "tom": { "age": "25" }, "mark": { "age": "30" } } }
292292
```
293-
but won't won't work in this case since there's an array in the path:
293+
but won't work in this case since there's an array in the path:
294294
```javascript
295295
{ "people": { "tom": [ { "age": "25" } ], "mark": [ { "age": "30" } ] } }
296296
```

0 commit comments

Comments
 (0)