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

Removing outdated limitations in Searchable Snapshots describing KNN is not compatible. #8817

Merged

Conversation

0ctopus13prime
Copy link
Contributor

Description

Since 2.18, now snapshot supports KNN index. Hence removing the comments saying KNN index is not supported.

Issues Resolved

opensearch-project/k-NN#2033

Version

2.18

Frontend features

N/A

Checklist

  • By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
    For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Copy link

Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged.

Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer.

When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review.

@0ctopus13prime 0ctopus13prime force-pushed the searchable-snapshot-knn branch from 8855962 to 1b42369 Compare November 26, 2024 00:31
…is not compatible.

Since 2.18, searchable snapshots is available with KNN

Signed-off-by: Dooyong Kim <[email protected]>
@0ctopus13prime 0ctopus13prime force-pushed the searchable-snapshot-knn branch from 1b42369 to 9151da8 Compare November 26, 2024 01:46
@kolchfa-aws
Copy link
Collaborator

@0ctopus13prime Is this PR ready for doc review?

@navneet1v
Copy link
Contributor

@0ctopus13prime Is this PR ready for doc review?

yes it is

Copy link
Collaborator

@kolchfa-aws kolchfa-aws left a comment

Choose a reason for hiding this comment

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

Thank you, @0ctopus13prime! One suggestion.

…hable_snapshot.md

Co-authored-by: kolchfa-aws <[email protected]>
Signed-off-by: Doo Yong Kim <[email protected]>
@0ctopus13prime
Copy link
Contributor Author

@kolchfa-aws
Updated accordingly! Thank you for the suggestion

Copy link
Collaborator

@natebower natebower left a comment

Choose a reason for hiding this comment

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

@kolchfa-aws kolchfa-aws added the backport 2.18 PR: Backport label for 2.18 label Dec 4, 2024
@kolchfa-aws kolchfa-aws merged commit 05d4125 into opensearch-project:main Dec 4, 2024
6 checks passed
opensearch-trigger-bot bot pushed a commit that referenced this pull request Dec 4, 2024
…is not compatible. (#8817)

* Removing outdated limitations in Searchable Snapshots describing KNN is not compatible.
Since 2.18, searchable snapshots is available with KNN

Signed-off-by: Dooyong Kim <[email protected]>

* Update _tuning-your-cluster/availability-and-recovery/snapshots/searchable_snapshot.md

Co-authored-by: kolchfa-aws <[email protected]>
Signed-off-by: Doo Yong Kim <[email protected]>

---------

Signed-off-by: Dooyong Kim <[email protected]>
Signed-off-by: Doo Yong Kim <[email protected]>
Co-authored-by: Dooyong Kim <[email protected]>
Co-authored-by: kolchfa-aws <[email protected]>
(cherry picked from commit 05d4125)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
github-actions bot pushed a commit that referenced this pull request Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 2.18 PR: Backport label for 2.18
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants