Skip to content

ESQL: EvalOperator should accept multiple fields instead of just one #104587

New issue
New issue
Open
Open
ESQL: EvalOperator should accept multiple fields instead of just one#104587
Labels
:Analytics/Compute EngineAnalytics in ES|QL>enhancementTeam:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)
@costin

Description

@costin
costin
opened on Jan 20, 2024

Description

Right now each field inside Eval is mapped to a separate 'EvalOperator' which makes the pipeline much larger than it has to be.
Instead only one EvalOperator per Eval should be created that incorporates all the evaluated fields in the same stage in the pipeline.

Metadata

Metadata

Assignees

No one assigned

    Labels

    :Analytics/Compute EngineAnalytics in ES|QL>enhancementTeam:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions