Skip to content

[FR] ES|QL Multi-stack Version Validation for Remote Functions #5411

@eric-forte-elastic

Description

@eric-forte-elastic

Repository Feature

Core Repo - (rule management, validation, testing, lib, cicd, etc.)

Problem Description

Currently the remote ES|QL validation for functions is specific only to one stack. The schemas are validated against multiple stack versions, as this can be simulated/emulated. However, a different approach may be needed for validating functions, such as for #5393 (ref), which needed to be min stacked at 9.2.0 and the remote stack needed to be 9.2.0+ in order for validation to pass.

Desired Solution

In an ideal world, we should check against each stack version using the min stack. However, this is not expected to be possible as it could quadruple the cost and time associated with this check. As such, an alternative means of validating an appropriate min_stack for functions is preferred.

Considered Alternatives

It is possible that we can map functions from the docs releases and do some for of min_stack validation against these (E.g.). However, since we cannot parse the functions themselves from the query without a parser this will be limited to a string based search, which will be less reliable.

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions