-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Fix LTR rescorer with model alias #126273
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
Conversation
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
Hi @afoucret, I've created a changelog YAML for you. |
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.
LGTM
@@ -247,8 +247,12 @@ setup: | |||
"learning_to_rank": { "model_id": "ltr-missing" } | |||
} | |||
} | |||
- match: { status: 404 } | |||
- match: { error.root_cause.0.type: "resource_not_found_exception" } | |||
- match: { error.root_cause.0.reason: "Could not find trained model [ltr-missing]" } |
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.
Non-blocking tip - you could optimize this with something like catch: /Could not find trained model \[ltr-missing\]
if you wanted to.
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.
+1
The YAML test are flaky in serverless. |
|
This PR fix a bug when using an LTR rescorer with a model alias where the user was seing the following error: