-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Closed
Labels
:Search Relevance/ES|QLSearch functionality in ES|QLSearch functionality in ES|QL>bugTeam:Search RelevanceMeta label for the Search Relevance team in ElasticsearchMeta label for the Search Relevance team in Elasticsearchpriority:normalA label for assessing bug priority to be used by ES engineersA label for assessing bug priority to be used by ES engineers
Description
Description
A simple query like the following will result in an error:
FROM books
| EVAL s = score(match(title, "Tolkien"))
error:
[2025-08-22T17:48:16,126][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [runTask-0] fatal error in thread [elasticsearch[runTask-0][search_coordination][T#1]], exiting java.lang.AssertionError: LuceneQueryEvaluator requires shard information
at org.elasticsearch.compute.lucene.LuceneQueryEvaluator.<init>(LuceneQueryEvaluator.java:57)
at org.elasticsearch.compute.lucene.LuceneQueryScoreEvaluator.<init>(LuceneQueryScoreEvaluator.java:35)
at org.elasticsearch.compute.lucene.LuceneQueryScoreEvaluator$Factory.get(LuceneQueryScoreEvaluator.java:71)
This most likely has to do with how Evals are pushed down, such that we then try to execute score without the shard information.
extract_snippet will most likely have the same error - so we should find a generic solution that can be applied to any function that requires shard info in order to be evaluated.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
:Search Relevance/ES|QLSearch functionality in ES|QLSearch functionality in ES|QL>bugTeam:Search RelevanceMeta label for the Search Relevance team in ElasticsearchMeta label for the Search Relevance team in Elasticsearchpriority:normalA label for assessing bug priority to be used by ES engineersA label for assessing bug priority to be used by ES engineers