Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Bug] Deleted rows take vector search top-k slots in data-evolution tables

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

Los mantenedores suelen responder en 3 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
57/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
cpp
Área
databases

Línea de trabajo

Start with LiveRowGlobalIndexReader::VisitVectorSearch and compare its vector path with the full-text path that loads live rows before searching shards. The issue suggests combining VectorSearch.pre_filter with shard live rows through ReplacePreFilter, using GlobalIndexLiveRowFilter::LiveRows, or loading live rows before fan-out. Add coverage for the reproduction with three deleted nearest rows and verify that a limit of 3 returns 3 live rows when enough matches pass the filters.

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

Descripción

bug
Search before asking
  • I searched in the issues and found nothing similar.
Paimon-cpp version

main at commit 50ef548ec87cc444a153fb2a03789f9be768d610, with #448 applied.

Minimal reproduce step
  1. Create a data-evolution table with row tracking and deletion-vectors.enabled = true. Write 10 rows with a vector column, then build a vector global index on that column.
  2. Delete the three rows nearest to a query vector, using deletion vectors.
  3. Search for that vector with limit = 3 through GlobalIndexScan::CreateReader → VisitVectorSearch.
  4. Pass the result to ScanContextBuilder::SetGlobalIndexResult, then scan and read.
What doesn't meet your expectations?

The index still ranks the deleted rows, so they take all three top-k slots. The read then drops them, because deletion vectors are applied only at read time. The query returns 0 rows instead of 3.

#448 (for #403) excludes deleted rows only from full-text ranking: LiveRowGlobalIndexReader::VisitVectorSearch delegates unchanged, and live rows are loaded only before a full-text search fans out to the shards. Java filters vector search with the same live rows (apache/paimon#8459).

Expected: limit = k returns k live rows whenever at least k live rows pass the search's pre_filter and predicate.

Anything else?

Follow-up of #403 / #448.

Suggestions:

  • VectorSearch already carries a pre_filter over global row ids, so LiveRowGlobalIndexReader::VisitVectorSearch can combine it with the live rows of the shard through ReplacePreFilter, reusing GlobalIndexLiveRowFilter::LiveRows, and pass the search on unchanged when the whole shard is live.
  • Load live rows on the visiting thread before a vector search fans out to the shards, as LiveRowUnionGlobalIndexReader does for full-text search.
Are you willing to submit a PR?
  • I'm willing to submit a PR!
Lenguaje dominante
C++
Estrellas
70
Forks
36
Merge medio
3 d 16 h
PR fusionados (30 d)
38

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 apache/paimon-cpp

Todos los issues de apache/paimon-cpp

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.