DOC-8634: numatrs should not be a request level parameter#203
Merged
Conversation
5 tasks
3 tasks
Contributor
Author
|
Checks are failing because the cb-swagger workflow no longer runs. I've updated the output documentation by hand. |
Contributor
Author
|
Merging because couchbase/docs-server#4030 is approved |
simon-dew
added a commit
that referenced
this pull request
Dec 9, 2025
* Update numatrs request-level parameter * Remove link to numatrs request-level parameter in Admin * Remove link to numatrs request-level parameter in Settings * Update output documentation
simon-dew
added a commit
that referenced
this pull request
Dec 9, 2025
* Remove link to numatrs request-level parameter in Admin * Remove link to numatrs request-level parameter in Settings * Update output documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jira issue: DOC-8634
The
numatrsrequest-level parameter still exists, but from discussion on the Jira ticket, it seems that it currently has no effect and is reserved for future use. I don't want to remove the request-level parameter from the documentation entirely, but I've updated its description as above, and removed the links to the request-level parameter from the equivalent node-level and cluster-level settings.Docs preview:
You will need the Docs Team credentials on Confluence.
This PR must be merged at the same time as the following:
Backport to the following branches:
release/7.0(unsupported)release/7.1(unsupported)In 7.6, the REST API specs were migrated to the
queryrepo. Merge to the following branches:trinitymorpheusAnd rebuild the
release/7.6,release/8.0, andcapellabranches here.