Skip to content

ES|QL: rule_execution_exception - Rule execution limit [100] reached #136599

@luigidellaquila

Description

@luigidellaquila

With CSV dataset

from languages_lookup_non_unique_ke* | enrich languages_policy on language_name | sort country DESC, language_code ASC NULLS LAST, language_name NULLS FIRST | limit 14081 | keep `language_name`, `country`, *, `country.keyword` | mv_expand country.keyword | grok language_name "%{WORD:YEcxuCOHsGzb} %{WORD:country.keyword}"| rename country.keyword as other1| rename language_code as other2 | lookup join multi_column_joinable_lookup on other1, other2 | where  NOT id_int <= 50 OR  NOT false AND  NOT other2 == 50 | where false AND  NOT true OR id_int > 50 AND true | where  NOT false AND other2 == 50
{
    "error": {
        "root_cause": [
            {
                "type": "rule_execution_exception",
                "reason": "Rule execution limit [100] reached"
            }
        ],
        "type": "rule_execution_exception",
        "reason": "Rule execution limit [100] reached"
    },
    "status": 500
}

See #136584

Metadata

Metadata

Assignees

No one assigned

    Labels

    :Analytics/ES|QLAKA ESQL>bugTeam:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)medium-riskAn open issue or test failure that is a medium risk to future releases

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions