MansiSingh17 commented on issue #18479: URL: https://github.com/apache/beam/issues/18479#issuecomment-4002134809
Hi @je-ik , thanks for thinking this through — the split you've outlined makes sense to me. Having the shared data objects (protobuf-based windowed values, watermarks, runtime metadata), the watermark manager interface, and the pipeline translator skeleton as the boundary between the two projects gives Project 2 a clear foundation to build on, and makes the interface contract explicit enough that design work can start in parallel. I'm fully aware of the dependency risk you mentioned — if Project 1 doesn't merge, Project 2 can't succeed. My plan would be to spend the first few weeks of the program in close coordination with @junaiddshaukat, designing and prototyping the stateful ParDo and splittable DoFn layers against the interfaces as they take shape, so there's no dead time waiting on merges. I'll start drafting a Project 2 proposal outline this week covering the scope, milestones, and how I'd handle the dependency. Happy to share it here for your feedback before I submit. -- 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]
