Skip to content
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

Update version for batch shard allocation to 2.14 #13469

Merged

Conversation

shiv0408
Copy link
Member

@shiv0408 shiv0408 commented Apr 30, 2024

Description

Update the version check for batch shard allocator to v2.14

Related Issues

Check List

  • New functionality includes testing.
    • All tests pass
  • New functionality has been documented.
    • New functionality has javadoc added
  • Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
  • Commits are signed per the DCO using --signoff
  • Commit changes are listed out in CHANGELOG.md file (See: Changelog)
  • Public documentation issue/PR created

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.

Copy link
Contributor

❌ Gradle check result for 4e5225b: 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?

Copy link
Contributor

github-actions bot commented May 1, 2024

❌ Gradle check result for fb721c4: 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?

@shiv0408 shiv0408 force-pushed the shard_batch_version_update branch from fb721c4 to 452ad26 Compare May 2, 2024 06:27
Copy link
Contributor

github-actions bot commented May 2, 2024

❌ Gradle check result for 452ad26: 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?

Copy link
Contributor

github-actions bot commented May 3, 2024

❌ Gradle check result for 452ad26: 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?

@shiv0408 shiv0408 force-pushed the shard_batch_version_update branch from 452ad26 to c074de9 Compare May 3, 2024 15:29
Copy link
Contributor

github-actions bot commented May 3, 2024

❌ Gradle check result for c074de9: 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?

shiv0408 added 2 commits May 6, 2024 14:16
Signed-off-by: Shivansh Arora <[email protected]>
@shiv0408 shiv0408 force-pushed the shard_batch_version_update branch from c074de9 to 8616644 Compare May 6, 2024 08:47
Copy link
Contributor

github-actions bot commented May 6, 2024

✅ Gradle check result for 8616644: SUCCESS

@shwetathareja shwetathareja merged commit 7c5739b into opensearch-project:main May 6, 2024
26 checks passed
@shiv0408 shiv0408 deleted the shard_batch_version_update branch May 6, 2024 19:12
finnegancarroll pushed a commit to finnegancarroll/OpenSearch that referenced this pull request May 10, 2024
…#13469)

* Update version for batch shard allocation to 2.14

Signed-off-by: Shivansh Arora <[email protected]>
deshsidd pushed a commit to deshsidd/OpenSearch that referenced this pull request May 17, 2024
…#13469)

* Update version for batch shard allocation to 2.14

Signed-off-by: Shivansh Arora <[email protected]>
parv0201 pushed a commit to parv0201/OpenSearch that referenced this pull request Jun 10, 2024
…#13469)

* Update version for batch shard allocation to 2.14

Signed-off-by: Shivansh Arora <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants