Bump OpenSearch to 2.19.3-1 (6.1)
#23483
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kingzacko1
changed the title
6.1)
dennisoelkers
requested changes
Aug 28, 2025
pom.xml
Outdated
|
|
||
| <!-- Dependencies --> | ||
| <opensearch.shaded.version>2.15.0-1</opensearch.shaded.version> | ||
| <opensearch.shaded.version>2.19.3-1</opensearch.shaded.version> |
Member
There was a problem hiding this comment.
This is just bumping the OpenSearch client we are using. Instead, we should set the OpenSearch version used in tests to 2.19.3. You can do this here.
Contributor
Author
There was a problem hiding this comment.
Made that change instead. Thank you! @dennisoelkers
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Bumping OpenSearch version to see if tests pass with upgraded version
/nocl testing
Motivation and Context
users facing issue resolved in opensearch-project/OpenSearch#14411. Seeing if 2.19.3 is compatible with 6.1 before advising upgrade.
How Has This Been Tested?
Screenshots (if appropriate):
this is the test
Types of changes
Checklist: