Search drops matches beyond the first 1,000 without saying so
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Read src/plugins/FluentCMS.Plugins.Search/SearchStore.cs, src/FluentCMS.Core/Content/Query/ContentQueryEngine.cs, and ContentQueryOptions.cs to trace the 1,000-result limit and query filters; coordinate with #3263, which changes the same path. Check the tests for each provider and add coverage for truncation reporting and site/state filters. Done means all acceptance criteria pass across every provider.
Written by the indexing model from the issue text.
Description
Problem
A search returns the 1,000 most recently indexed matches (src/plugins/FluentCMS.Plugins.Search/SearchStore.cs:31-34, src/FluentCMS.Core/Content/Query/ContentQueryEngine.cs:96-97,244); filters, row rules and paging then run over those ids. Matches beyond the first 1,000 are lost and total is understated, with nothing in the answer saying so. The cut is a stated trade-off (ContentQueryOptions.cs:34-37); the silence is the defect.
Proposal
- Report truncation in the list answer when the index returned its maximum.
- Push the site and state filters into the index query so the 1,000 are spent on rows the caller can get.
Done together with #3263, which changes the same query path.
Acceptance
- A query with more than the maximum matches says the result is truncated
- Entries of other sites or states do not consume the maximum
- Tests on every provider
Found in the code review of 17 Nov 2026.
- Dominant language
- C#
- Stars
- 569
- Forks
- 107
- Avg merge
- 2h 49m
- Merged PRs (30d)
- 397
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fluentcms/FluentCMS
-
area:host area:operations type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:build security type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:sdk security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:content security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area:build type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in fluentcms/FluentCMS
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
microsoft/microsoft-ui-reactor#1567 ·
Maintainers usually reply within 1 day
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw-windows-node#2287 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
kind:ux needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
elsa-workflows/elsa-foundation#4742 ·
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement good first issue help wanted new-language
Difficulty 2/5 1-3 hours Newbie friendliness 82/100