Skip to content

ESQL: use the correct upper limit for topN for mv_expand queries #101266

New issue
New issue
Closed
Closed
ESQL: use the correct upper limit for topN for mv_expand queries#101266
Assignees
costin
Labels
:Analytics/ES|QLAKA ESQL>bugTeam:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)low-riskAn open issue or test failure that is a low risk to future releases
@astefan

Description

@astefan
astefan
opened on Oct 24, 2023

Description

Following #100782 in certain scenarios the "default" limit used for the TopN at Lucene level is too broad. This should be aligned with the logic in the Analyzer.AddImplicitLimit rule.

Metadata

Metadata

Assignees

Labels

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

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions