DanielLeens commented on issue #11184: URL: https://github.com/apache/seatunnel/issues/11184#issuecomment-4805646634
Thanks for writing this up in a structured way. I checked both this roadmap issue and the current state of PR #11174. This is worth keeping as a design-track issue rather than treating it as a generic feature request. The phased breakdown is useful, and the most important part is that the current merge boundary stays tight. From a maintainer perspective, the practical next step is: 1. keep the must-land scope for #11174 limited to the Spark 4.1 correctness and release path already identified here 2. move the deferred Phase 2+ items into smaller follow-up issues after the current PR lands, so review does not get blocked by too much long-tail work at once 3. keep backward compatibility for Spark 2.4 / 3.3 explicit in every follow-up, especially around starter resolution, packaging, and JDK requirements So the direction here makes sense. Once #11174 is merged, it would help to split the remaining roadmap items into separate linked tracking issues by topic: test hardening, starter-common decoupling, translation deduplication, and longer-term streaming evolution. -- 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]
