Support multiword and query-time synonyms with explicit scoring semantics
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start with the public API in ts/native.ts, the engine implementation in src/engine.rs, and the wrapper contract in README.md; compare their synonym behavior with the assessed revision. Then design and test position/phrase semantics, bounded query-time expansion, deduplication, and scoring across the listed interactions. Done means indexing, searching, tracing, persistence versioning where needed, and documentation consistently implement the accepted semantics.
由索引模型根据 Issue 内容生成。
描述
Outcome
Support multiword and query-time synonyms with explicit scoring semantics.
Current behavior
Verified by source inspection of the public API and native implementation at the assessed revision; no runtime reproduction was performed. Synonym sources and replacements must each analyze to one term. Expansion is index-time only, and changing rules requires rebuilding; stacked alternatives also affect BM25 field length.
Acceptance criteria
- Design multiword synonym matching with explicit token-position/graph and phrase semantics.
- Add a bounded query-time expansion option so supported rule changes can avoid an index rebuild.
- Define directional/equivalent rules, expansion deduplication, maximum expansion, and scoring consequences.
- Keep indexing, searching, and tracing consistent for synonym-derived spans; version persisted semantics where necessary.
- Test phrases, stop words, fuzzy/prefix interactions, and relevance effects; document this as wrapper design work, not a turnkey Tantivy synonym feature.
References and scope
Parent: Epic: Extend fulltext search capabilities beyond the initial wrapper API.
Wrapper contract. This is proposed standalone-library capability with no committed release. Application-specific authorization, source projection, and product API integration are outside this issue.
Comment generated by kAIle (GPT-6)
- 主要语言
- Rust
- 星标
- 3
- 派生
- 0
- 平均合并
- 15 小时 12 分钟
- 30 天内合并 PR
- 11
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
HarperFast/fulltext 的其他 Issue
-
难度 5/5 一周以上 新手友好度 25/100
HarperFast/fulltext#76 · 5 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 42/100
HarperFast/fulltext#74 ·
维护者通常 1 天内回复
-
Qualify Tantivy pruning for small-window ordinary ANY searches可能已有人在做 @kylebernhardy 于 9 天前认领。 未关闭
难度 5/5 一周以上 新手友好度 25/100
HarperFast/fulltext#73 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Qualify Tantivy 0.27 upgrade and enforce the analyzer rebuild boundary可能已有人在做 @kylebernhardy 于 15 天前认领。 未关闭dependencies
HarperFast/fulltext#71 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Expose trace progress and per-record truncation for bounded highlight recovery可能已有人在做 @kylebernhardy 于 7 天前认领。 未关闭
难度 5/5 一周以上 新手友好度 35/100
HarperFast/fulltext#68 · 1 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 HarperFast/fulltext 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 65/100
swc-project/swc-ai-issues#432 ·
-
SPLADE `/embed_sparse` output depends on the other inputs in the batch (candle BertModel / DistilBertModel)可能已有人在做 @0z5a 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
huggingface/text-embeddings-inference#979 ·
维护者通常 1 天内回复
-
good first issue help wanted
难度 2/5 1-3 小时 新手友好度 78/100
servo/rust-smallvec#874 ·
-
难度 1/5 1 小时以内 新手友好度 94/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 2 天内回复