-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add took time to request nodes stats #15054
Conversation
❌ Gradle check result for f97cb0e: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #15054 +/- ##
============================================
+ Coverage 71.80% 71.88% +0.08%
- Complexity 62775 62845 +70
============================================
Files 5169 5169
Lines 294665 294688 +23
Branches 42616 42616
============================================
+ Hits 211574 211828 +254
+ Misses 65678 65433 -245
- Partials 17413 17427 +14 ☔ View full report in Codecov by Sentry. |
Please don't forget to add this to https://github.com/opensearch-project/opensearch-api-specification. |
❌ Gradle check result for 93ac279: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
@jainankitk done. Looks like |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be great to get a yaml test to verify the request response looks how you want it to look but changes LGTM
server/src/main/java/org/opensearch/action/search/SearchRequestStats.java
Show resolved
Hide resolved
❕ Gradle check result for 93ac279: 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. |
The backport to
To backport manually, run these commands in your terminal: # Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.x
# Create a new branch
git switch --create backport/backport-15054-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 76b9931299b4a45308b7ede4659e750eacd5006a
# Push it to GitHub
git push --set-upstream origin backport/backport-15054-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.x Then, create a pull request where the |
@dzane17 could you please open a manual backport PR for this? And please make sure to open the api-spec PR as well. |
Signed-off-by: David Zane <davizane@amazon.com> (cherry picked from commit 76b9931)
@dblock I added a nested field in the nodes stats response, have not changed any APIs. Is api-spec needed? I noticed existing nodes stats tests don't reach the nesting depth of my change so was not what to build off of. |
Signed-off-by: Jay Deng <jayd0104@gmail.com>
It adds a new field to the response object, right? Therefore it's an API change (albeit a backwards compatible one). Def add a test that reaches deeper! |
Signed-off-by: David Zane <davizane@amazon.com>
Signed-off-by: Jay Deng <jayd0104@gmail.com>
Signed-off-by: David Zane <davizane@amazon.com>
Signed-off-by: Jay Deng <jayd0104@gmail.com>
Signed-off-by: David Zane <davizane@amazon.com>
Signed-off-by: Jay Deng <jayd0104@gmail.com>
Description
Add overall took stats to request nodes/stats API output.
Related Issues
Resolves #10768
Check List
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.