Skip to content

Commit 145dd9a

Browse files
authored
Update search-howto-index-cosmosdb.md
Clarification for supportability purposes about null value behavior.
1 parent 56f964e commit 145dd9a

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/search/search-howto-index-cosmosdb.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.custom:
1010
- devx-track-dotnet
1111
- ignite-2023
1212
ms.topic: how-to
13-
ms.date: 01/18/2024
13+
ms.date: 06/17/2024
1414
---
1515

1616
# Index data from Azure Cosmos DB for NoSQL for queries in Azure AI Search
@@ -302,6 +302,7 @@ The following example shows a [data source definition](#define-the-data-source)
302302
" highWaterMarkColumnName": "_ts"
303303
},
304304
```
305+
Note that when you assign a `null` value to a field in your Azure Cosmos DB, the AI Search indexer is unable to distinguish between `null` and a missing field value. Therefore, if a field in the index is empty, it will not be substituted with a `null` value, even if that modification was specifically made in your database.
305306

306307
<a name="IncrementalProgress"></a>
307308

0 commit comments

Comments
 (0)