Epic: Extend fulltext search capabilities beyond the initial wrapper API

Abierto
  • ¿Algo no está bien?
#49 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
node.js, rust
Área
backend, search

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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)

Lenguaje dominante
Rust
Estrellas
3
Forks
0
Merge medio
15 h 12 min
PR fusionados (30 d)
11

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de HarperFast/fulltext

Todos los issues de HarperFast/fulltext

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.