hubcio opened a new issue, #3560:
URL: https://github.com/apache/iggy/issues/3560

   Umbrella tracking issue for the Kafka-wire-protocol gateway (`gateways/`), 
letting existing Kafka clients talk to Iggy unmodified.
   
   Seed design + TCP listener lands in #3421.
   
   Goal: implement enough of the Kafka wire protocol that standard Kafka 
producers/consumers (and admin tools) work against Iggy via a bridge, then 
document migration off Kafka.
   
   ## Sub-issues
   
   Foundation:
   
   - [ ] #3421 - TCP listener for Kafka clients (seed)
   - [ ] #3533 - IggyBridge core: SDK client + stream/topic mapping
   
   Phase 1 - core wire APIs + tooling:
   
   - [ ] #3534 - Metadata API (key 3): broker/topic discovery
   - [ ] #3535 - Produce API (key 0): bridge to `send_messages`
   - [ ] #3536 - Fetch API (key 1): bridge to offset-based polling
   - [ ] #3537 - ListOffsets API (key 2): earliest/latest via high watermark
   - [ ] #3538 - CreateTopics API (key 19): stream/topic provisioning
   - [ ] #3539 - Phase 1: docker-compose, E2E tests, quick-start docs
   
   Phase 2 - consumer groups + offsets:
   
   - [ ] #3540 - design: consumer offset persistence strategy
   - [ ] #3541 - FindCoordinator, JoinGroup, SyncGroup, Heartbeat
   - [ ] #3542 - OffsetCommit + OffsetFetch with persisted offsets
   - [ ] #3543 - LeaveGroup + rebalance semantics
   - [ ] #3544 - Phase 2: E2E tests with consumer groups
   
   Admin + extended APIs:
   
   - [ ] #3545 - transactional APIs: UNSUPPORTED_VERSION stub + idempotence docs
   - [ ] #3546 - DeleteTopics, DescribeConfigs, AlterConfigs
   - [ ] #3547 - DeleteRecords: trim topic to offset via retention
   - [ ] #3548 - DescribeGroups + ListGroups
   
   Auth + migration:
   
   - [ ] #3549 - Kafka SASL auth bridge to Iggy users
   - [ ] #3550 - migration guide: dual-write, cutover, decommission
   
   ## Status
   
   Stays open until boxes above are checked or de-scoped.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to