-
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
[Backport 2.x] Support multi ranges traversal when doing date histogram rewrite optimization (#13317) #13522
[Backport 2.x] Support multi ranges traversal when doing date histogram rewrite optimization (#13317) #13522
Conversation
2d1e7f4
to
2d66adb
Compare
…mization (opensearch-project#13317) Signed-off-by: bowenlan-amzn <[email protected]> remove unnecessary change log Signed-off-by: bowenlan-amzn <[email protected]>
2d66adb
to
faf44dd
Compare
❌ Gradle check result for 2d66adb: 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 faf44dd: 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 faf44dd: 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 2d1e7f4: TIMEOUT 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 faf44dd: 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: bowenlan-amzn <[email protected]>
faf44dd
to
fdbbd83
Compare
❌ Gradle check result for fdbbd83: 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 fdbbd83: 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 fdbbd83: 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 @@
## 2.x #13522 +/- ##
============================================
+ Coverage 71.28% 71.32% +0.04%
- Complexity 60145 61171 +1026
============================================
Files 4957 5026 +69
Lines 282799 287653 +4854
Branches 41409 42058 +649
============================================
+ Hits 201591 205172 +3581
- Misses 64189 65166 +977
- Partials 17019 17315 +296 ☔ View full report in Codecov by Sentry. |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.14 2.14
# Navigate to the new working tree
pushd ../.worktrees/backport-2.14
# Create a new branch
git switch --create backport/backport-13522-to-2.14
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ab620026b7a0cc8d47a1327c2550680d4d6f132a
# Push it to GitHub
git push --set-upstream origin backport/backport-13522-to-2.14
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.14 Then, create a pull request where the |
Description
Manual backport because auto backport failed #13317 (comment)
Related Issues
Resolves #[Issue number to be closed when this PR is merged]
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.