-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Modify create snapshot v2 response when wait_for_completion is false #15499
Modify create snapshot v2 response when wait_for_completion is false #15499
Conversation
Signed-off-by: Anshu Agarwal <anshukag@amazon.com>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #15499 +/- ##
============================================
- Coverage 71.91% 71.83% -0.08%
+ Complexity 63311 63286 -25
============================================
Files 5225 5225
Lines 296350 296352 +2
Branches 42809 42810 +1
============================================
- Hits 213119 212896 -223
- Misses 65743 66008 +265
+ Partials 17488 17448 -40 ☔ View full report in Codecov by Sentry. |
Regarding CodeCov failure: changes are covered in integ tests. |
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-15499-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 c37d5f691fabb470181b7333efce5bbe4b058107
# Push it to GitHub
git push --set-upstream origin backport/backport-15499-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 |
…ensearch-project#15499) Signed-off-by: Anshu Agarwal <anshukag@amazon.com> Co-authored-by: Anshu Agarwal <anshukag@amazon.com>
…ensearch-project#15499) Signed-off-by: Anshu Agarwal <anshukag@amazon.com> Co-authored-by: Anshu Agarwal <anshukag@amazon.com>
…ensearch-project#15499) Signed-off-by: Anshu Agarwal <anshukag@amazon.com> Co-authored-by: Anshu Agarwal <anshukag@amazon.com>
…ensearch-project#15499) Signed-off-by: Anshu Agarwal <anshukag@amazon.com> Co-authored-by: Anshu Agarwal <anshukag@amazon.com>
Description
With current implementation of shallow snapshot v2, the create api respond with snapshot info details irrespective of value set for
wait_for_completion
in the request.Expected Response
For shallow snapshots v2, if
wait_for_completion=false
, the api response should beif
wait_for_completion=true
, the api response should beRelated Issues
#15516
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.