You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ioanatia I don't think it's the same - in EVAL we would get a true or false, as full text functions are boolean functions. Using score function allows to get the score part in EVAL but not the result of the full text function itself.
If you want to evaluate in an EVAL whether author:"tolkien" is true, doesn't it suffice to just check if it's score is bigger than 0?
I am not sure how it's different.
Activity
elasticsearchmachine commentedon Mar 24, 2025
Pinging @elastic/es-analytical-engine (Team:Analytics)
elasticsearchmachine commentedon Mar 24, 2025
Pinging @elastic/kibana-esql (ES|QL-ui)
ioanatia commentedon Jul 7, 2025
I wonder if we can close this one if favour of using the score function #120082
With the score function we can have:
which would be the equivalent of what this issue is proposing.
carlosdelest commentedon Jul 7, 2025
@ioanatia I don't think it's the same - in EVAL we would get a true or false, as full text functions are boolean functions. Using score function allows to get the score part in EVAL but not the result of the full text function itself.
ioanatia commentedon Jul 7, 2025
If you want to evaluate in an EVAL whether
author:"tolkien"
is true, doesn't it suffice to just check if it's score is bigger than 0?I am not sure how it's different.
carlosdelest commentedon Jul 7, 2025
It's not the same as in the type returned is not the one the function provides. A boolean function should evaluate to a boolean, not a number IMO.
ioanatia commentedon Jul 7, 2025
is
m
supposed to be a boolean in this example? or something else?because in the case of using the score function,
m
here is a boolean: