-
Notifications
You must be signed in to change notification settings - Fork 138
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] NeuralSearch Plugin Cannot Invoke Predict API for Sparse Model #3321
Comments
@zhichao-aws @xinyual could you guys please take a look? |
Hi @bzhangam @dhrubo-os I've taken a look at the issue and here are some key findings:
The bug should be caused by ml-commons side change. Will you fix it? @bzhangam |
Hi @zhichao-aws. Thanks for your investigation. I'm not working on the ml-commons plugin. @dhrubo-os Do you know who can work on it? |
I'm looking into this, will update once i have something |
Resolved with: opensearch-project/neural-search#1055 Issue was caused due to conflicts in jackson dependency versions across ml-commons, core and neural-search. Updated to use the version coming from core for consistency. |
@dhrubo-os Let's close this issue, thank you! |
What is the bug?
On 12/31/2024 we start seeing an error related to Neural Sparse Query.
We have got the below error logs:
The issue happens when Neural plugin tries to invoke the ML predict API to inference the data. (code)
We have raised an empty change PR to confirm the issue should not be caused by the change in the Neural Search plugin. Since the last PR merged into the Neural Search plugin on 12/27/2024 did pass all the tests.
How can one reproduce the bug?
It’s a consistent issue that can happen when we try to use a sparse model to inference the data in Neural plugin. (we can reproduce it locally by following this doc)
What is the expected behavior?
What is your host/environment?
Do you have any screenshots?
N/A
Do you have any additional context?
If we directly invokes ML predict API to use a sparse model to inference the data it can work. (we can follow this doc to do that)
The text was updated successfully, but these errors were encountered: