-
Notifications
You must be signed in to change notification settings - Fork 143
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
Issue 1878/1879/1880 fixing index not found for model group/model/tasks #1889
Issue 1878/1879/1880 fixing index not found for model group/model/tasks #1889
Conversation
Signed-off-by: Samuel Herman <sherman8915@gmail.com>
Signed-off-by: Samuel Herman <sherman8915@gmail.com>
Signed-off-by: Samuel Herman <sherman8915@gmail.com>
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #1889 +/- ##
=========================================
Coverage 82.63% 82.64%
Complexity 5391 5391
=========================================
Files 521 521
Lines 21724 21731 +7
Branches 2211 2211
=========================================
+ Hits 17952 17959 +7
Misses 2873 2873
Partials 899 899
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@@ -162,7 +166,8 @@ public void search(SearchRequest request, ActionListener<SearchResponse> actionL | |||
} | |||
} | |||
|
|||
private QueryBuilder rewriteQueryBuilder(QueryBuilder queryBuilder, List<String> modelGroupIds) { | |||
@VisibleForTesting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the neural search guys told me to try not to use this, but ok
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-1889-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 41fac826c8fd1182f83c1f3f6b301bf17022eb2f
# Push it to GitHub
git push --set-upstream origin backport/backport-1889-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x Then, create a pull request where the |
@samuel-oci Seems there are some conflicts for 2.x. Can you help manually backport this PR to 2.x ? |
@ylwu-amzn what is the process? should I just create the backport branch and send the PR? |
@samuel-oci no need to create backport branch in ml-commons branch, just use your forked repo like this PR |
…ks (opensearch-project#1889) * adding tests for search of ML constructs Signed-off-by: Samuel Herman <sherman8915@gmail.com> * improve test coverage on MLSearchHandler Signed-off-by: Samuel Herman <sherman8915@gmail.com> * fix headers on test Signed-off-by: Samuel Herman <sherman8915@gmail.com> --------- Signed-off-by: Samuel Herman <sherman8915@gmail.com> (cherry picked from commit 41fac82) Signed-off-by: Samuel Herman <sherman8915@gmail.com>
@ylwu-amzn created #1895 |
…ks (opensearch-project#1889) * adding tests for search of ML constructs Signed-off-by: Samuel Herman <sherman8915@gmail.com> * improve test coverage on MLSearchHandler Signed-off-by: Samuel Herman <sherman8915@gmail.com> * fix headers on test Signed-off-by: Samuel Herman <sherman8915@gmail.com> --------- Signed-off-by: Samuel Herman <sherman8915@gmail.com>
Description
When model/model group/task is not created yet, return an empty search response instead of a broken 404 with cryptic index not found message.
More description in:
#1878
#1879
#1880
Issues Resolved
#1878
#1879
#1880
Check List
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.