Extend filter metadata with exact integers, dates, IPs, JSON paths, and hierarchical facets

Abierto
  • ¿Algo no está bien?
#57 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
Bastante claro
Estado de actividad
Activo
Stack tecnológico
node.js, rust
Área
api, database, search

Línea de trabajo

Start with the public API in ts/native.ts and the native implementation in src/engine.rs, then review the wrapper contract in README.md. The issue calls for defining several new value and query contracts plus protocol and schema versioning, so first map how the existing metadata is represented and persisted. Done means the listed acceptance criteria are implemented, documented, and covered by boundary, reopen-compatibility, and rebuild-error tests.

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

Descripción

Outcome

Extend filter metadata with exact integers, dates, IPs, JSON paths, and hierarchical facets.

Current behavior

Verified by source inspection of the public API and native implementation at the assessed revision; no runtime reproduction was performed. Filter metadata currently supports string, number (f64), and Boolean values. There are no public exact 64-bit integer, date, IP, JSON-path, or hierarchical facet types.

Acceptance criteria

  • Define lossless Node-to-Rust representations for signed/unsigned 64-bit integers, avoiding unsafe JavaScript-number coercion.
  • Define explicit date precision/timezone and IP normalization/range semantics.
  • Add an explicitly scoped JSON-path and hierarchical facet schema/query contract, including missing and multivalued semantics.
  • Version the packed protocol and persisted schema identity; test boundaries, reopen compatibility, and rebuild errors.
  • Document numeric timestamps as an existing date workaround and distinguish exact typed values from analyzed text.

References and scope

Parent: Epic: Extend fulltext search capabilities beyond the initial wrapper API.

Tantivy capability. 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.