Skip to content

Onboarding new maven snapshots publishing to s3 (jVector) - #178

Merged
sam-herman merged 1 commit into
opensearch-project:mainfrom
peterzhuamazon:maven-snapshots-s3
Oct 15, 2025
Merged

Onboarding new maven snapshots publishing to s3 (jVector)#178
sam-herman merged 1 commit into
opensearch-project:mainfrom
peterzhuamazon:maven-snapshots-s3

Conversation

@peterzhuamazon

Copy link
Copy Markdown
Member

Description

Onboarding new maven snapshots publishing to s3 (jVector)

Related Issues

opensearch-project/opensearch-build#5360

Check List

  • New functionality includes testing.
  • New functionality has been documented.
  • API changes companion pull request created.
  • Commits are signed per the DCO using --signoff.
  • 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.

Comment thread DEVELOPER_GUIDE.md
```

### 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/)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

provide the new link in maven?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated.

Signed-off-by: Peter Zhu <zhujiaxi@amazon.com>
@sam-herman
sam-herman merged commit f4cbfd9 into opensearch-project:main Oct 15, 2025
9 of 39 checks passed
@github-project-automation github-project-automation Bot moved this from 👀 In Review to ✅ Done in Engineering Effectiveness Board Oct 15, 2025
@opensearch-trigger-bot

Copy link
Copy Markdown
Contributor

The backport to 2.19 failed:

The process '/usr/bin/git' failed with exit code 1

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.19

Then, create a pull request where the base branch is 2.19 and the compare/head branch is backport/backport-178-to-2.19.

@opensearch-trigger-bot

Copy link
Copy Markdown
Contributor

The backport to 3.0 failed:

The process '/usr/bin/git' failed with exit code 1

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.0

Then, create a pull request where the base branch is 3.0 and the compare/head branch is backport/backport-178-to-3.0.

@peterzhuamazon

Copy link
Copy Markdown
Member Author

@peterzhuamazon
peterzhuamazon deleted the maven-snapshots-s3 branch October 15, 2025 18:46
@peterzhuamazon

peterzhuamazon commented Oct 15, 2025

Copy link
Copy Markdown
Member Author

Re-published 3.0 core and the jvector published as well:

@opensearch-trigger-bot

Copy link
Copy Markdown
Contributor

The backport to 3.0 failed:

The process '/usr/bin/git' failed with exit code 1

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.0

Then, create a pull request where the base branch is 3.0 and the compare/head branch is backport/backport-178-to-3.0.

akash-shankaran pushed a commit to akash-shankaran/opensearch-jvector that referenced this pull request Oct 16, 2025
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

2 participants