-
Notifications
You must be signed in to change notification settings - Fork 25.7k
ES|QL: Enable score function in release builds #136988
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
Co-authored-by: Tommaso Teofili <tommaso.teofili@elastic.co>
|
Hi @ioanatia, I've created a changelog YAML for you. |
🔍 Preview links for changed docs |
ℹ️ Important: Docs version tagging👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version. We use applies_to tags to mark version-specific features and changes. Expand for a quick overviewWhen to use applies_to tags:✅ At the page level to indicate which products/deployments the content applies to (mandatory) What NOT to do:❌ Don't remove or replace information that applies to an older version 🤔 Need help?
|
|
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
|
Pinging @elastic/kibana-esql (ES|QL-ui) |
|
@stratoula enabling the score function means that we also change the validation rules for the search functions like match. these can now be used in EVALs, as arguments of the score function, e.g.: |
|
@ioanatia here is our PR elastic/kibana#240933. Let me know when to merge |
carlosdelest
left a comment
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.
Don't we need to update rest-api-spec/test/esql/60_usage.yml as well to ensure we're tracking telemetry? 🤔
tteofili
left a comment
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, thanks @ioanatia
It's better to be sure so I have run the release tests and they pass - so I think it's not needed. |
## Summary Updated the locations to support full text search functions in eval <img width="933" height="228" alt="image" src="https://github.com/user-attachments/assets/0810221c-1006-489e-908d-57a8d3e49344" /> With this PR elastic/elasticsearch#136988 we will be able to have MATCH, KQL etc in EVAL.
## Summary Updated the locations to support full text search functions in eval <img width="933" height="228" alt="image" src="https://github.com/user-attachments/assets/0810221c-1006-489e-908d-57a8d3e49344" /> With this PR elastic/elasticsearch#136988 we will be able to have MATCH, KQL etc in EVAL.
## Summary Updated the locations to support full text search functions in eval <img width="933" height="228" alt="image" src="https://github.com/user-attachments/assets/0810221c-1006-489e-908d-57a8d3e49344" /> With this PR elastic/elasticsearch#136988 we will be able to have MATCH, KQL etc in EVAL.
## Summary Updated the locations to support full text search functions in eval <img width="933" height="228" alt="image" src="https://github.com/user-attachments/assets/0810221c-1006-489e-908d-57a8d3e49344" /> With this PR elastic/elasticsearch#136988 we will be able to have MATCH, KQL etc in EVAL.
This enables the score function in release builds.
The score function can be used to retrieve the score of individual queries, which is helpful for applying custom scoring formulas or for debugging / score explainability.