junaiddshaukat commented on issue #18479:
URL: https://github.com/apache/beam/issues/18479#issuecomment-3861434712
Hi, I'm interested in working on the portable Kafka Streams Runner
as part of GSoC 2026 (if it got selected).
I've been contributing to the Apache Beam TypeScript SDK — my merged
PRs include LRU cache eviction for CachingStateProvider (#37214) and
CombinePerKeyPrecombineOperator (#37466). I'm now ramping up on the
Beam portability framework and Kafka Streams to prepare for this project.
I've read through the design document and the previous attempts by
Kai Jiang and Kyle Winkelman. A few questions:
1. Should the GSoC skeleton target the portable runner API (Fn API /
gRPC), or a classic translation-based approach?
2. What's the minimum set of transforms the skeleton should support —
Read, ParDo, GroupByKey?
3. Is there a preference for using the Kafka Streams DSL vs the
lower-level Processor API for the translation layer?
I'll be studying the Flink portable runner as a reference implementation.
Happy to discuss the design further.
--
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]
