Support snapshot continuation for sorted searches

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
15/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
rust, typescript
领域
search

调研方向

Start with the SearchPageRequest definition in ts/native.ts (around line 297), which omits sort and aggregations, and the sentence about snapshot continuation in src/DESIGN.md (line 233). The work is a design decision first: how a continuation token carries the last sort-key tuple and ID while keeping snapshot binding and HMAC coverage, and whether aggregations appear only on page one. Done means that design is agreed in the issue, and the issue is still backlog because no consumer is waiting.

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

描述

Summary

searchPage cannot be combined with sort or aggregations, so a sorted result set cannot be traversed past the offset window. This is a documented limit with no tracking issue.

  • SearchPageRequest omits sort and aggregations (ts/native.ts:297).
  • src/DESIGN.md:233: "Sorted snapshot continuation and metadata-derived score adjustment remain outside this increment."

The score-adjustment half of that sentence is tracked in Add bounded metadata-derived score adjustment for business ranking #51. This issue is for the continuation half.

Scope

  • A continuation token for sorted searches that carries the last sort-key tuple and ID, with the same snapshot binding and HMAC coverage as relevance traversal.
  • Decide whether aggregations are returned on the first page only.

Consumer status

No consumer is waiting. Harper orders stored-field sorts itself in Allow stored-field sorting and exact counts for full-text search #3846 and has not adopted native sort. File this as backlog until that changes.

Issue generated by kAIle (Claude Fable 5.2)

主要语言
Rust
星标
3
派生
0
平均合并
20 小时 29 分钟
30 天内合并 PR
13

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

HarperFast/fulltext 的其他 Issue

查看 HarperFast/fulltext 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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