Large number of excludedPaths in index policy fails creation

[jamesjhhan]

Describe the bug Creating or updating a container with an indexing policy with a large number of excludedPaths (around 900) times out. There is no issue in the non-docker Windows cosmos emulator as well as the cloud service. Also, it seems to work fine under 850 excludedPaths.

To Reproduce Steps to reproduce the behavior:

1. create a container with a indexingPolicy with 900 or more excludedPaths (either via code or using the localhost:8081 dashboard).
2. the request times out.

Expected behavior Container should be created/updated with the specifiedd indexing policy without timing out.

Desktop (please complete the following information):

• OS: Windows 11

Docker Images Used:

• Linux

**Arguments && Environment variables to start Docker:

Docker Environment

• Docker compose   Additional context docker-compose.yml here:

Cosmosdb

cosmosdb: restart: always container_name: "azure-cosmosdb-emulator" hostname: "azurecosmosemulator" image: 'mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:latest' mem_limit: 8GB tty: true ports:

• 8081:8081 # Data Explorer
• 8900:8900
• 8901:8901
• 8902:8902
• 10250:10250
• 10251-10251
• 10252:10252
• 10253:10253
• 10254:10254
• 10255:10255
• 10256:10256
• 10350:10350 environment:
  • AZURE_COSMOS_EMULATOR_ENABLE_DATA_PERSISTENCE=true
  • AZURE_COSMOS_EMULATOR_IP_ADDRESS_OVERRIDE=127.0.0.1
  • COSMOS_KEY=**** volumes:
    • cosmos-data:/tmp/cosmos

volumes: cosmos-data: driver: local