Add paths to _cluster/stats API for metric filtering.

[SwethaGuptha]

Description

Add rest API specs for new URI paths added to _cluster/stats API for metric filtering in #15938.

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

Check List

• Functionality includes testing.
• API changes companion pull request created, if applicable.
• Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

❕ Gradle check result for e29169a: UNSTABLE

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.95%. Comparing base (ad7f9e7) to head (e29169a).
Report is 111 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #16425      +/-   ##
============================================
- Coverage     72.05%   71.95%   -0.11%     
+ Complexity    64861    64789      -72     
============================================
  Files          5309     5309              
  Lines        302734   302785      +51     
  Branches      43733    43750      +17     
============================================
- Hits         218134   217854     -280     
- Misses        66731    67044     +313     
- Partials      17869    17887      +18     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dbwiddis]

LGTM. Does this need a documentation change?

[SwethaGuptha]

LGTM. Does this need a documentation change?

Documentation change PR has been raised: opensearch-project/documentation-website#8595

[SwethaGuptha]

@dbwiddis can you help in closing this review if there are no other concerns?

[dbwiddis]

@dbwiddis can you help in closing this review if there are no other concerns?

Please complete the checklist in the PR template.

1. Needs a change log entry before I can do anything with it. I assume this is targeted to 2.x as well?
2. Should there also be a corresponding change to the REST API spec here?

[SwethaGuptha]

Apologies for the delayed response.

Please complete the checklist in the PR template.

1. Needs a change log entry before I can do anything with it.  I assume this is targeted to 2.x as well?

Is this still required?

2. Should there also be a corresponding change to the REST API spec [here](https://github.com/opensearch-project/opensearch-api-specification/)?

Being addressed in opensearch-project/opensearch-api-specification#639

[dbwiddis]

1. Needs a change log entry before I can do anything with it.  I assume this is targeted to 2.x as well?

Is this still required?

The changelog verifier workflow is required to pass before it can be merged. In order for that to happen, either a changelog entry (for the appropriate version) must exist for the PR, or the skip-changelog tag must be added. "For the appropriate vresion" is determined by the presence of a backport-2.x tag.

While I could make assumptions here, my intent was to find out from you which of those options was the correct one to take, rather than guessing.

Being addressed in opensearch-project/opensearch-api-specification#639

Thanks, would be great if you could edit the PR description where there's a checkbox for the API spec and link to it there... or just check the box like the one for documentation website is checked.

I'm still a bit confused about whether (and if so, why) we are maintaining these specs in two different places (rest-api-spec and the opensearch-api-specification repo). As I have been the only maintainer to review this, I was leaving it open for other maintainers to look at.

[opensearch-trigger-bot]

This PR is stalled because it has been open for 30 days with no activity.