Hey y'all, please vote to adopt KIP-382 by replying +1 to this thread. For your reference, here are the highlights of the proposal:
- Leverages the Kafka Connect framework and ecosystem. - Includes both source and sink connectors. - Includes a high-level driver that manages connectors in a dedicated cluster. - High-level REST API abstracts over connectors between multiple Kafka clusters. - Detects new topics, partitions. - Automatically syncs topic configuration between clusters. - Manages downstream topic ACL. - Supports "active/active" cluster pairs, as well as any number of active clusters. - Supports cross-data center replication, aggregation, and other complex topologies. - Provides new metrics including end-to-end replication latency across multiple data centers/clusters. - Emits offsets required to migrate consumers between clusters. - Tooling for offset translation. - MirrorMaker-compatible legacy mode. Thanks, and happy holidays! Ryanne
