Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[NIDX-04 workstream] Replace the Stream element index

Chiusa
  • Qualcosa non va?
#14,004 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Refactoring
Chiarezza
Da chiarire
Stato di attività
Attiva
Ambito
databases, search

Direzione di ricerca

Leggere il design di BDB-NIDX-SPEC-001 revisione 0.2 e ispezionare l’entry point banyand/stream.newElementIndex dopo la chiusura di #14003. L’issue richiede una scomposizione in attività foglia ordinate e non bloccate, con seam denominati e comandi RED/e2e; il completamento significa che native role e tutte le suite elencate fixture, NRT, analyzer, posting, sort, restart, receive, race e compatibility superano i test.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bydb file compatible change database

[NIDX-04 workstream] Replace the Stream element index

Parent: #13990
Blocked by: #14003

Tracking parent — do not apply Backlog. Split this workstream only after NIDX-03 closes, using the actual native writer, reader, posting, and receive seams then present on main.

End-state boundary

banyand/stream.newElementIndex selects the native idx batch writer, filter executor, posting collector, sorter, snapshot path, restart path, and external receiver.

Required behavior

  • Committed batches become visible at the documented near-real-time boundary.
  • Exact, existence, range, AND/OR/NOT, HAVING, IN, prefix, wildcard, and MATCH return fixed document-ID sets.
  • Keyword, simple, standard, and URL analysis produce fixed terms; MATCH AND/OR overrides remain distinct.
  • Document-ID/timestamp postings and ascending/descending doc-value sort are deterministic.
  • Legacy/native snapshots and raw segments are cross-readable; interrupted receive never publishes partial data.
  • Scoring, phrase/fuzzy/geo, highlighting, facets, explanations, collectors, and plugins remain absent.

Just-in-time decomposition gate

After #14003 closes, file ordered leaves around live Stream callers and one observable feature each. Every leaf needs a pre-agreed seam, literal terms/document IDs, a RED command, an e2e command, resource/concurrency bounds, and same-file rollback. Do not merge analyzers, filters, postings, sorters, or receiver code without activating a production path. Apply Backlog to one unblocked leaf only.

Completion criteria

All future leaves merge; the complete newElementIndex role is native; fixture, NRT, analyzer, posting, sort, restart, receive, race, and compatibility suites pass; and this workstream closes before NIDX-05 decomposition.

Lexical non-regression

Repository changes for every implementation leaf before the final removal may delete existing references but must add zero new case-insensitive bluge tokens and zero matching tracked paths. The gate includes imports and aliases, function/type/variable names, filenames and runtime names, strings, comments and messages, tests, fixture/provenance data, scripts, configuration, and generated assets. Compatibility evidence uses neutral legacy oracle or compatibility writer labels plus an immutable revision or content hash rather than adding a retired module name.

This lexical gate applies to repository changes, not to issue or archived-design prose that names the dependency in order to specify its removal.

Design

BDB-NIDX-SPEC-001 revision 0.2 — NIDX-04 behavior

Lingua principale
Java
Stelle
25k
Fork
6.6k
Merge medio
12h 28m
PR unite (30g)
31

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/skywalking

Tutte le issue di apache/skywalking

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.