Skip to content

ESQL: null compared to integer fails for argument types mismatch for unmapped fields #142115

@astefan

Description

@astefan

Description

This is mentioned in #141870 as well, but I believe it's better treated as a standalone issue.

SET unmapped_fields="nullify";
from date_nanos,multivalue_geometries
| eval  `id` = "ZLDFWGgAeqXyGijMeIE", snrydVVhJWe = num, BrxbmpzIZHH = num - num, intersects = "SPiZIPzQbCfiCLj", millis = case(baz > 72, "high", "low"), `contains` = num * num - num, zToxMOHPUNDY = 8091896195626274881

results in

"type" : "verification_exception",
            "reason" : "Found 1 problem\nline 1:197: first argument of [baz > 72] is [null] so second argument must also be [null] but was [integer]",
            "stack_trace" : "org.elasticsearch.xpack.esql.VerificationException: Found 1 problem\nline 1:197: first argument of [baz > 72] is [null] so second argument must also be [null] but was [integer]

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions