Epic: Extend fulltext search capabilities beyond the initial wrapper API

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Read the public wrapper API in ts/native.ts, the native engine in src/engine.rs, and protocol limits in src/protocol.rs to understand the existing capabilities. This epic lists many broad features but leaves acceptance criteria to child issues, so choose a scoped child issue before making changes; its criteria should define what done looks like.

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

描述

Outcome

Track the remaining search capabilities identified by comparing the wrapper with Tantivy 0.26.2, plus wrapper-specific highlighting, traversal, and synonym extensions.

In scope

  • Facets/aggregations and native sorting/business ranking.
  • Versioned per-field analyzers, phrase proximity, configurable fuzzy matching, richer typed queries, and score explanations.
  • Additional metadata types and filter predicates.
  • Boolean match tracing, bounded deep-result traversal/autocomplete qualification, and multiword/query-time synonyms.

Out of scope

  • Existing BM25, Boolean text expressions, typed exact/numeric-range filters, lifecycle, and checkpoint-publication implementation.
  • Stored authoritative documents, alternate storage backends, and distributed search.
  • Consumer-specific source projection, authorization, and product API integration.
  • Consumer release commitments.

Delivery and priority

This is a follow-up backlog, not a committed release. Start with sorting and facets/aggregations, then phrase/fuzzy controls and explanations; move analyzer work earlier when a multilingual requirement is established. Each child issue defines its own acceptance criteria and resource limits. Multiword synonyms and snapshot traversal require wrapper design; they are not turnkey Tantivy APIs.

Source-inspection baseline: public wrapper API, native engine, and protocol limits. Runtime behavior was not independently exercised for this backlog.

Comment generated by kAIle (GPT-6)

主要语言
Rust
星标
3
派生
0
平均合并
15 小时 12 分钟
30 天内合并 PR
11

环境准备

  • 没有 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 摘要。