[Bug]: `max-query-parallelism` accepts values outside documented 1-8 range

Open Beginner friendly
#3,570 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
csharp
Domain
api, backend

Research direction

Start at DAB's config deserialization for max-query-parallelism and trace where its documented range is represented. Add coverage for values 0 and 9, then verify that out-of-range values are rejected while values from 1 through 8 remain accepted.

Written by the indexing model from the issue text.

Description

2.x health-endpoint

The docs state the valid range for max-query-parallelism is 1-8. However, both 0 and 9 are accepted without error.

Expected

DAB should reject values outside the 1-8 range at config deserialization.

Actual

Value Result
0 Accepted, DAB starts, health checks run (9 checks returned)
9 Accepted, DAB starts, health checks run (9 checks returned)

Impact: max-query-parallelism=0 is particularly concerning — it's unclear whether this means "no parallelism" (sequential) or "unlimited parallelism". Testing showed health checks still execute and return results, so 0 likely defaults to some internal value.

Dominant language
C#
Stars
1.5k
Forks
372
Avg merge
3d 8h
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/data-api-builder

All issues in Azure/data-api-builder

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.