-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Fixed RRF YAML REST Test: rrf with pinned retriever as a sub-retriever
#130402
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
Fixed RRF YAML REST Test: rrf with pinned retriever as a sub-retriever
#130402
Conversation
|
Pinging @elastic/search-eng (Team:SearchOrg) |
|
Pinging @elastic/search-relevance (Team:Search - Relevance) |
|
Hi @mridula-s109, I've created a changelog YAML for you. |
...plugin/rank-rrf/src/yamlRestTest/resources/rest-api-spec/test/rrf/950_pinned_interaction.yml
Show resolved
Hide resolved
...plugin/rank-rrf/src/yamlRestTest/resources/rest-api-spec/test/rrf/950_pinned_interaction.yml
Show resolved
Hide resolved
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.
Agree with Mike on the changelog entry. Thanks for resolving the issue!
...plugin/rank-rrf/src/yamlRestTest/resources/rest-api-spec/test/rrf/950_pinned_interaction.yml
Show resolved
Hide resolved
a4503f4 to
9125b38
Compare
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.
Pull Request Overview
This PR un-mutes the 950_pinned_interaction.yml test and fixes its assertions by removing the default retriever, using match_none for the nested standard retriever, and updating the expected hits.
- Unmutes the failing YAML REST test for pinned sub-retriever
- Removes the initial standard retriever and replaces its nested query with
match_none - Updates assertions to expect only two pinned documents
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| x-pack/plugin/rank-rrf/src/yamlRestTest/resources/rest-api-spec/test/rrf/950_pinned_interaction.yml | Removed default retriever, replaced nested query with match_none, and updated hit assertions |
| muted-tests.yml | Removed mute entry for rrf with pinned retriever as a sub-retriever test |
Comments suppressed due to low confidence (2)
x-pack/plugin/rank-rrf/src/yamlRestTest/resources/rest-api-spec/test/rrf/950_pinned_interaction.yml:86
- [nitpick] Consider adding a brief comment explaining why
match_noneis used here to clarify that the default retriever should return no documents.
match_none: {}
x-pack/plugin/rank-rrf/src/yamlRestTest/resources/rest-api-spec/test/rrf/950_pinned_interaction.yml:88
- [nitpick] The test no longer verifies hit scores; consider re-adding an assertion for the expected scores or ordering to ensure scoring behavior is still correct.
- match: { hits.total.value: 2 }
...plugin/rank-rrf/src/yamlRestTest/resources/rest-api-spec/test/rrf/950_pinned_interaction.yml
Outdated
Show resolved
Hide resolved
…d-retriever-as-a-sub-retriever
…d-retriever-as-a-sub-retriever
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
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, thank you for the iterations!
💔 Backport failed
You can use sqren/backport to manually backport by running |
…er` (elastic#130402) * fixed failing pinned retriever test * Update docs/changelog/130402.yaml * Delete docs/changelog/130402.yaml * Worked on the PR comments * Fixed the Match_none * space format * space format
…er` (elastic#130402) * fixed failing pinned retriever test * Update docs/changelog/130402.yaml * Delete docs/changelog/130402.yaml * Worked on the PR comments * Fixed the Match_none * space format * space format # Conflicts: # muted-tests.yml
…er` (elastic#130402) * fixed failing pinned retriever test * Update docs/changelog/130402.yaml * Delete docs/changelog/130402.yaml * Worked on the PR comments * Fixed the Match_none * space format * space format # Conflicts: # muted-tests.yml
What does this PR do?
How was this verified?