Skip to content

ESQL: unmapped_fields="load" should work with full-text search/MATCH #144121

@alex-spies

Description

@alex-spies

Follow-up to #141927, except that we should make load work with as many full-text search functions as makes sense.

Full-text functions that don't reference a missing or partially mapped field are the lowest hanging fruit and we should be able to just enable that after adding a couple of tests. E.g. WHERE existing_field:"some search phrases".

It's less clear what to do with full-text functions that may refer to a missing/partially mapped field inside the query string, like in WHERE KQL("missing_field: foobar").

C.f. docs for full-text functions

Metadata

Metadata

Assignees

No one assigned

    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