Search drops matches beyond the first 1,000 without saying so

未关闭
#3,302 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
csharp
领域
backend, search

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

area:content plugin type:bug

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.

主要语言
C#
星标
569
派生
107
平均合并
2 小时 49 分钟
30 天内合并 PR
397

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

fluentcms/FluentCMS 的其他 Issue

查看 fluentcms/FluentCMS 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。