-
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
Support wildcard/regex for indices param in _remotestore/_restore #8922
Support wildcard/regex for indices param in _remotestore/_restore #8922
Conversation
Gradle Check (Jenkins) Run Completed with:
|
85c230d
to
61aa234
Compare
Gradle Check (Jenkins) Run Completed with:
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #8922 +/- ##
============================================
+ Coverage 71.42% 71.66% +0.24%
- Complexity 59978 61106 +1128
============================================
Files 4985 5052 +67
Lines 282275 287122 +4847
Branches 40946 41602 +656
============================================
+ Hits 201603 205771 +4168
- Misses 63999 64322 +323
- Partials 16673 17029 +356 ☔ View full report in Codecov by Sentry. |
61aa234
to
0a5e37a
Compare
Gradle Check (Jenkins) Run Completed with:
|
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.
This PR is stalled because it has been open for 30 days with no activity. Remove stalled label or comment or this will be closed in 7 days. |
0a5e37a
to
92f112f
Compare
Integ tests for this already existed before my change but were skipped due to AwaitsFix annotation. I've remove this and now these tests are run as part of gradle check. |
❌ Gradle check result for 56d100a: 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? |
@linuxpi Thanks for checking on the test failure, I've restarted the gradle-check workflow |
❌ Gradle check result for 56d100a: 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? |
Signed-off-by: Varun Bansal <[email protected]>
@linuxpi Please investigate the tests failures after the results come back:
Check will keep failing until you've rebased. |
❌ Gradle check result for e1f55c6: 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? |
❌ Gradle check result for e1f55c6: 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? |
❕ Gradle check result for 488ab9c: 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-8922-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 29ebd80fdd6771ccc2023bf432977c38c76bfd55
# Push it to GitHub
git push --set-upstream origin backport/backport-8922-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#8922) * Support wildcard/regex for indices param in _remotestore/_restore Signed-off-by: bansvaru <[email protected]> (cherry picked from commit 29ebd80)
backport pr #13527 |
…ensearch-project#8922) * Support wildcard/regex for indices param in _remotestore/_restore Signed-off-by: Varun Bansal <[email protected]> (cherry picked from commit 29ebd80)
) (#13527) * Support wildcard/regex for indices param in _remotestore/_restore Signed-off-by: Varun Bansal <[email protected]> (cherry picked from commit 29ebd80)
…ensearch-project#8922) * Support wildcard/regex for indices param in _remotestore/_restore Signed-off-by: bansvaru <[email protected]>
…ensearch-project#8922) * Support wildcard/regex for indices param in _remotestore/_restore Signed-off-by: bansvaru <[email protected]>
…ensearch-project#8922) * Support wildcard/regex for indices param in _remotestore/_restore Signed-off-by: bansvaru <[email protected]>
Description
{ "indices": ["my-index-*"] }
will match all indices whose name start withmy-index-
and trigger remote store restore.Related Issues
Resolves #8480
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.