You have a database in an Azure Cosmos DB for NoSQL account. The database contains a container named container1. The indexing mode of container1 is set to none. You configure Azure Cognitive Search…

Question

Options

• AModify the index attributes in Cognitive Search to Searchable
• BModify the index attributes in Cognitive Search to Retrievable
• CModify the indexing policy of container1 to exclude the /* path
• DChange the indexing mode of container1 to consistent

• A
  2% (1)
• B
  2% (1)
• C
  2% (1)
• D
  93% (43)

Explanation

Azure Cognitive Search uses a Cosmos DB indexer that reads documents from the container. When the Cosmos DB container's indexing mode is set to 'none', Cosmos DB does not maintain an internal index, and the indexer's change-detection mechanism (which relies on the _ts timestamp and the ability to query documents) cannot enumerate or retrieve documents reliably. Changing the indexing mode to 'consistent' re-enables Cosmos DB's internal indexing so the Cognitive Search indexer can successfully crawl and index the container's data. Modifying Cognitive Search index attributes (Searchable/Retrievable) or the Cosmos DB index path exclusions would not fix the root cause.

No community discussion yet for this question.