Skip to content

[DOCS] Clarify negative scores returned by Elastic Rerank #3000

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

Closed
wants to merge 1 commit into from

Conversation

charlotte-hoblik
Copy link

Added a note clarifying that relevance scores produced during reranking can include negative values.
Based on https://github.com/elastic/search-docs-team/issues/234

@charlotte-hoblik charlotte-hoblik added backport-8.16 Automated backport with mergify backport-8.17 Automated backport with mergify backport-8.18 Automated backport with mergify labels Mar 21, 2025
@charlotte-hoblik charlotte-hoblik self-assigned this Mar 21, 2025
@charlotte-hoblik charlotte-hoblik requested a review from a team as a code owner March 21, 2025 15:30
Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@charlotte-hoblik
Copy link
Author

Negative scores are not possible starting from 8.16.4: elastic/elasticsearch#125415 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.16 Automated backport with mergify backport-8.17 Automated backport with mergify backport-8.18 Automated backport with mergify
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant