Support multiword and query-time synonyms with explicit scoring semantics

Abierto
  • ¿Algo no está bien?
#61 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
Bien especificado
Estado de actividad
Activo
Stack tecnológico
node.js, rust
Área
backend, search

Línea de trabajo

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.

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

Descripción

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)

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.