Define how schema discovery identifies virtual and optional fields

Aperta
  • Qualcosa non va?
#929 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
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
rust
Ambito
cli, databases

Direzione di ricerca

Begin with the central plan in #939 and review the retained original evidence in #840. Verify the response metadata and real discovery samples before proposing a reliable distinction between virtual fields and optional presence; done means an agreed detection rule and display/export behavior.

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

Descrizione

Release triage — 2026-09-21

Moved to v0.5.1 follow-up triage, outside the v0.5.0 release gate. Time-boxed investigation: obtain supported virtual/optional-field metadata semantics. Record evidence and close or split concrete follow-up work; do not infer virtual fields from names or nullability.

This schedules follow-up investigation, not a claim that a code fix is known or authorization for new production probes. Existing prerequisites and ownership remain in force. Central plan: #939.

Earlier scope and evidence (preserved)

Deferred by owner — 2026-09-18

Defer virtual/optional-field metadata investigation. #928 can be explained and designed, but must not assume a virtual-field detection rule.

Keep open and outside the current implementation queue. This is a priority/design deferral, not a claim that the issue is fixed or an upstream blocked label request. Revisit explicitly after the ready work; central plan: #939.

Earlier scope and evidence (preserved)

Focused scope — 2026-09-15

Deferred until the direction below is resolved.

Split from #840: virtual fields and optional field presence must not be confused with Nullable types.

Acceptance criteria

Verify response metadata and real discovery samples; distinguish known virtual fields without dropping arbitrary underscore-prefixed user columns; decide display/export behavior.

Direction needed

Need reliable virtual-field metadata and agreed display meaning; current Optional forwarding is not proven wrong.

Split from #840. Original evidence is retained there. This scope supersedes any broader suggestions in that report.

Lingua principale
Rust
Stelle
80
Fork
9
Merge medio
3g 20h
PR unite (30g)
57

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 ClickHouse/clickhousectl

Tutte le issue di ClickHouse/clickhousectl

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.