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

Explore schema-assisted ClickPipe creation

Aperta
  • Qualcosa non va?
#928 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à
Attiva
Stack tecnologico
rust
Ambito
cli, cloud

Direzione di ricerca

Start with the cloud clickpipe schema-discover object-storage SERVICE_ID ... --json entry point and the corresponding ClickPipe creation workflow. Agree the supported UX, source scope, field selection, conflict rules, and virtual-field handling before implementation. Done means explicit-column creation still works, the chosen discovery-to-creation mapping is tested, and a useful example is documented.

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

Descrizione

enhancement good first issue

Deferred to v0.5.1 — 2026-09-21

Moved from v0.5.0 to v0.5.1 under the owner's latest instruction: work not being implemented for the current release belongs in the follow-up milestone. This supersedes the earlier request to keep it in v0.5.0.

This remains an enhancement and good first issue: schema-assisted ClickPipe creation is a convenience, not a missing fix in #979. No implementation PR exists, and no additional v0.5.0 PR is planned. The assignee still needs to agree the supported sources, UX, field selection, conflict handling and virtual/nullability rules before coding. Existing explicit-column create and schema discovery work.

Keep open for the new-engineer handoff; the owner selects the assignee. Follow-up tracker: #939. v0.5.0 acceptance is now solely #757.

Earlier design discussion (superseded where it assumes a required file interface)

Missing workflow, with an example — 2026-09-18

Design discussion remains open. No new input format or flag is approved, and no implementation was made.

What users can do today

cloud clickpipe schema-discover object-storage SERVICE_ID ... --json returns an object containing discovered fields, for example (illustrative, not a new live capture):

{"fields":[{"name":"id","type":"UInt64","optional":false},{"name":"event_time","type":"DateTime","optional":false}]}

To create the corresponding object-storage pipe, users must currently transcribe destination columns into flags such as:

--column 'id:UInt64' --column 'event_time:DateTime'

Object-storage create now correctly requires columns, and discovery itself works. The missing enhancement is a supported way to save discovery output and reuse selected columns at create time without manually retyping a large schema. --table-definition-file describes table engine/keys/TTL; it is not a direct import of the discovery response. The whole-pipe update --file path is also not a create-time discovery importer.

Behavior to discuss

An initial version could read a discovery JSON file (or stdin), convert chosen fields to destination columns, and use them when creating the pipe. Flag spelling is intentionally undecided. It should not silently copy every discovery field: virtual metadata fields may need different treatment, and optional is not enough to infer all destination/virtual semantics (related #929).

Decisions still needed
  1. Accept the complete discovery response, a simpler columns-only file, or both?
  2. Import all eligible fields or require an explicit selection/exclusion mechanism?
  3. Reject combining imported columns with --column, or define a clear merge/duplicate-name rule?
  4. How should virtual fields and optional/nullability metadata be represented? #929's metadata investigation is deferred; do not guess from underscore prefixes.
  5. Should the first version support only the object-storage workflow that raised this issue, or all compatible create commands?

Next step: choose the smallest useful workflow after reviewing this example. Subsequent tests must cover malformed files, stdin, duplicate columns, selection rules and exact creation payloads. Keep this as a convenience enhancement, not a claim that schema discovery or explicit-column create is broken.

Earlier scope and evidence (preserved)

Focused scope — 2026-09-15

Deferred until the direction below is resolved.

Split from #840: avoid manual transcription of discovered columns into repeated flags.

Acceptance criteria

Choose accepted schema/file format, stdin behavior, merge/conflict rules with --column and virtual-field selection.

Direction needed

Need an input contract and explicit treatment of discovered virtual fields.

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
4g 13h
PR unite (30g)
59

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.