-
Notifications
You must be signed in to change notification settings - Fork 123
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
[BUG] unable to import knn searchPipeline and ml methods #940
Comments
@toyaokeke which version of the client are you using? We're testing the 3.0.0 beta that has these endpoints generated from the OpenSearch Spec. |
hi @nhtruong , thank you for the quick response 🙏🏿 |
@toyaokeke Can you please try the 3.0 beta? Does it fix your problem? |
appears to work as expected. is there an ETA of when there will be a non-beta release? |
The current beta version is going to be very close to the final version. We're trying to get more people to test the beta before releasing it. We're aiming to release by year end. |
perfect, thank you! if you like we can mark this as closed since it will be resolved with the latest release |
Thanks. I'll leave this open in case other people have the same question before release. |
What is the bug?
A clear and concise description of the bug.
the methods in the
knn
,searchPipeline
andml
are not available for importHow can one reproduce the bug?
Steps to reproduce the behavior.
What is the expected behavior?
A clear and concise description of what you expected to happen.
What is your host/environment?
Operating system, version.
"@opensearch-project/opensearch": "~2.13.0"
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.
The text was updated successfully, but these errors were encountered: