Skip to content

fix single-shot queries exceeding the per-query maximum for concatenated feature types - #678

Merged
azahnen merged 3 commits into
masterfrom
max-features-per-query-concat
Oct 30, 2026
Merged

azahnen merged 3 commits into
masterfrom
max-features-per-query-concat

Conversation

@cportele

Copy link
Copy Markdown
Contributor

For a feature type with more than one main table (type-level concat), every main table was capped with the full maxFeaturesPerSubQuery, so a single-shot query could return n times the maximum. Bounded counts, one main table after the other, now distribute the maximum across the main tables; tables are skipped once it is reached. Types with a single main table are unchanged.

…ted feature types

For a feature type with more than one main table (type-level concat), every
main table was capped with the full maxFeaturesPerSubQuery, so a single-shot
query could return n times the maximum. Bounded counts, one main table after
the other, now distribute the maximum across the main tables; tables are
skipped once it is reached. Types with a single main table are unchanged.
@cportele cportele self-assigned this Oct 28, 2026
@cportele cportele added the bug label Oct 28, 2026
@cportele
cportele requested a review from azahnen as a code owner October 28, 2026 14:00

@azahnen azahnen left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works as expected.

@azahnen
azahnen enabled auto-merge (squash) October 30, 2026 09:33
@azahnen
azahnen merged commit a7941d4 into master Oct 30, 2026
3 checks passed
@azahnen
azahnen deleted the max-features-per-query-concat branch October 30, 2026 09:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants