Onboarding new maven snapshots publishing to s3 (jVector) - #178
Merged
sam-herman merged 1 commit intoOct 15, 2025
Merged
Conversation
peterzhuamazon
requested review from
jimdickinson,
sam-herman and
tjake
as code owners
October 15, 2025 17:02
sam-herman
reviewed
Oct 15, 2025
| ``` | ||
|
|
||
| ### Install jVector KNN within your existing OpenSearch cluster installation | ||
| The jvector plugin can be downloaded from [here](https://central.sonatype.com/service/rest/repository/browse/maven-snapshots/org/opensearch/knn/opensearch-jvector/3.0.0.0-SNAPSHOT/) |
Collaborator
There was a problem hiding this comment.
provide the new link in maven?
Signed-off-by: Peter Zhu <zhujiaxi@amazon.com>
peterzhuamazon
force-pushed
the
maven-snapshots-s3
branch
from
October 15, 2025 18:38
e896be4 to
d71ff50
Compare
sam-herman
approved these changes
Oct 15, 2025
Contributor
|
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.19 2.19
# Navigate to the new working tree
cd .worktrees/backport-2.19
# Create a new branch
git switch --create backport/backport-178-to-2.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 f4cbfd9403db3c845bfa0630e8ce94482a0b2635
# Push it to GitHub
git push --set-upstream origin backport/backport-178-to-2.19
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.19Then, create a pull request where the |
Contributor
|
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-3.0 3.0
# Navigate to the new working tree
cd .worktrees/backport-3.0
# Create a new branch
git switch --create backport/backport-178-to-3.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 f4cbfd9403db3c845bfa0630e8ce94482a0b2635
# Push it to GitHub
git push --set-upstream origin backport/backport-178-to-3.0
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-3.0Then, create a pull request where the |
Member
Author
Member
Author
|
Re-published 3.0 core and the jvector published as well: |
Contributor
|
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-3.0 3.0
# Navigate to the new working tree
cd .worktrees/backport-3.0
# Create a new branch
git switch --create backport/backport-178-to-3.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 f4cbfd9403db3c845bfa0630e8ce94482a0b2635
# Push it to GitHub
git push --set-upstream origin backport/backport-178-to-3.0
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-3.0Then, create a pull request where the |
akash-shankaran
pushed a commit
to akash-shankaran/opensearch-jvector
that referenced
this pull request
Oct 16, 2025
…-project#178) Signed-off-by: Peter Zhu <zhujiaxi@amazon.com>
sam-herman
added a commit
that referenced
this pull request
Oct 16, 2025
* changes to perform JVector 3.2 upgrade Signed-off-by: Akash Shankaran <akash.shankaran@ibm.com> * fix failing workflow, and spotless apply Signed-off-by: Akash Shankaran <akash.shankaran@ibm.com> * few more package upgrades for JDK24 Signed-off-by: Akash Shankaran <akash.shankaran@ibm.com> * add Akash as maintainer (#174) * add Akash as maintainer * change to IBM --------- Signed-off-by: Samuel Herman <sherman8915@gmail.com> * update akash in codeowners (#176) Signed-off-by: Samuel Herman <sherman8915@gmail.com> * Onboarding new maven snapshots publishing to s3 (jVector) (#178) Signed-off-by: Peter Zhu <zhujiaxi@amazon.com> * increment version of jVector to support incremental construction (#167) persist neighbors cache add support for sorted index searcher fixes for resolving the node -> docId add incremental merge construction with leading segment move additional tests to internal test for transparency update documentation add readme pictures remove doc values by default separate docIdtoOrdMap class and add tests Signed-off-by: Samuel Herman <sherman8915@gmail.com> * update changelog Signed-off-by: Akash Shankaran <akash.shankaran@ibm.com> --------- Signed-off-by: Akash Shankaran <akash.shankaran@ibm.com> Signed-off-by: Samuel Herman <sherman8915@gmail.com> Signed-off-by: Peter Zhu <zhujiaxi@amazon.com> Co-authored-by: sam-herman <97131656+sam-herman@users.noreply.github.com> Co-authored-by: Peter Zhu <zhujiaxi@amazon.com>
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
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
Onboarding new maven snapshots publishing to s3 (jVector)
Related Issues
opensearch-project/opensearch-build#5360
Check List
--signoff.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.