FMX commented on PR #2813: URL: https://github.com/apache/celeborn/pull/2813#issuecomment-2558840667
> QQ: Why are we moving spark-3 to spark-3-4 ? It is possible that spark-4 impl ends up evolving nontrivially in time, and in a manner which conflicts with spark-3. > > Do we want to simply keep spark-3 (which eventually goes away when support for spark-3.5 is dropped), and start with a new spark-4 ? > > I understand the duplication aspect could be nontrivial - wondering if there is a middle ground for 3.5 vs 4, which minimizes this. > > This would also minimize impact on existing spark-3 users (from dep pov) The main reason to add a module to share within spark 3.5 and spark 4 is because the shuffle APIs are stable. The unstable APIs are in the columnar shuffle module which is separated from the module of spark 3.5. -- 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]
