Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

v0.21 lane: migrate/kc CLI

オープン
  • 何か問題がありますか？
#3,003 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
18/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
go, kafka
領域
cli, data-engineering

調査の方向性

Start with the parent issue #3002, ROADMAP.md, and the prior design document at docs/design-documents/20260722-debezium-compete-roadmap.md. The issue requires a new CLI contract, report schema, and error codes before implementation, with mappings, tests, and documentation spanning several connector types. Done means the listed commands, compatibility reporting, per-connector tests, guides, and other definition-of-done items are complete.

索引モデルが issue の本文から書いたものです。

説明

roadmap

Roadmap item: v0.21: migrate/kc CLI. Parent: #3002. Plan: ROADMAP.md (#2945).

Goal

Ship conduit migrate kafka-connect v1 plus conduit kc lint and conduit kc diff. migrate reads Kafka Connect worker and connector configs and emits Conduit pipeline config and a compatibility report. It never silently drops config it cannot translate. It covers exactly the connectors certified in this release: Debezium Postgres and MySQL, JDBC source and sink, S3 sink, Elasticsearch/OpenSearch sink, Kafka to Kafka. kc lint includes KIP-1188 override risks; kc diff diffs connector-config versions and checks schema compatibility against the registry.

Risk tier

Tier 2 (CLI). The compatibility report schema and error codes are public contracts.

Definition of done

  • Every command supports --json; every error has a stable code, the failing config path and a suggested fix (CLAUDE.md).
  • The report lists every input key as translated, mapped with a note, or untranslatable. A test fails if any key is unaccounted for.
  • Unit tests per connector mapping; golden-file tests for the emitted pipelines.
  • Docs: the 'Migrating from Kafka Connect' concept mapping (worker to instance, task to pipeline, SMT to processor, converter to schema) and per-connector guides for the v0.21 set; llms.txt updated with the docs.
  • Concept mapping page states plainly that only Postgres resumes from imported offsets in v0.21; every other migration re-snapshots.
  • Tests: unit and integration green with the race detector; every bug fix ships with the test that would have caught it.
  • Docs move with the code: conduit.io docs source and llms.txt updated, changelog entry.
  • Lint clean; PR descriptions carry the roadmap item, risk tier, adversarial self-review and, for Tier 1, a failure-mode analysis.

Linked issues and PRs

No existing issue; this issue is the tracker. SMT pack (v0.22) is #2960 and is out of scope here. Prior design context: docs/design-documents/20260722-debezium-compete-roadmap.md.

Dependencies on other lanes

Defines the connector set that migrate emits, so every certification lane depends on its mapping tables. Depends on the migration harness lane for the diff-based tests. Offset import for Postgres is wired in through the Postgres lane, and the Debezium output mode through #3032.

Design document

Required: a CLI contract, a report schema and error codes. Design doc in docs/design-documents/ with problem, constraints, at least two alternatives, failure modes (malformed input, unknown connector classes, secrets in configs), upgrade/rollback and observability.

Owner

Agent lane, DeVaris sign-off for Tier 1.

🤖 Generated with Claude Code

https://claude.ai/code/session_01SvPfP7eL7SskkoptXvAYCH

主要言語
Go
スター
614
フォーク
66
平均マージ
1日 4時間
マージ済み PR（30日）
69

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

ConduitIO/conduit のほかの issue

ConduitIO/conduit の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。