Skip to content

Commit 20c4423

Browse files
authored
Merge pull request #90569 from bleroy/beleroy/cognitive-search-warning-incremental-progress
Common warning about Cognitive Search Cosmos DB incremental progress
2 parents 34dba36 + 7444420 commit 20c4423

File tree

1 file changed

+12
-1
lines changed

1 file changed

+12
-1
lines changed

articles/search/cognitive-search-common-errors-warnings.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -205,4 +205,15 @@ In the example LanguageDetectionSkill below, the `'text'` input field may trigge
205205
If you want to ensure that all text is analyzed, consider using the [Split skill](cognitive-search-skill-textsplit.md).
206206

207207
### Web API skill response contains warnings
208-
Indexer was able to run a skill in the skillset, but the response from the Web API request indicated there were warnings during execution. Review the warnings to understand how your data is impacted and whether or not action is required.
208+
Indexer was able to run a skill in the skillset, but the response from the Web API request indicated there were warnings during execution. Review the warnings to understand how your data is impacted and whether or not action is required.
209+
210+
### The current indexer configuration does not support incremental progress
211+
This warning only occurs for Cosmos DB data sources.
212+
213+
Incremental progress during indexing ensures that if indexer execution is interrupted by transient failures or execution time limit, the indexer can pick up where it left off next time it runs, instead of having to re-index the entire collection from scratch. This is especially important when indexing large collections.
214+
215+
The ability to resume an unfinished indexing job is predicated on having documents ordered by the `_ts` column. The indexer uses the timestamp to determine which document to pick up next. If the `_ts` column is missing or if the indexer can't determine if a custom query is ordered by it, the indexer starts at beginning and you'll see this warning.
216+
217+
It is possible to override this behavior, enabling incremental progress and suppressing this warning by using the `assumeOrderByHighWatermarkColumn` configuration property.
218+
219+
[More information about Cosmos DB incremental progress and custom queries.](https://go.microsoft.com/fwlink/?linkid=2099593)

0 commit comments

Comments
 (0)