HeartSaVioR edited a comment on pull request #34089: URL: https://github.com/apache/spark/pull/34089#issuecomment-1033397906
Sorry for the post-review. I'm not a PMC member so I have no idea about the discussion history in private@ (apologize if there were discussions and decisions about this), but have we discussed thoughtfully about dependency upgrades? IMHO, when we deal with major version upgrade, I'd like to see thoughtful experiments on production usage (at least stage) for while before getting into it. Kafka 3.1 was released just 2 weeks ago while Kafka 3.0 was released around 4 months ago (which is still a bit short term to stabilize), so I'd feel safer on 3.0.x at least, and honestly, 2.8.x unless it blocks something. (If there was no release on 3.0.x, I'm not sure what happens. We may want to see why they didn't go through bugfix versions and just go through new minor version. Did they figure out any critical/blocker issues about Kafka 3.0 after release? If then isn't it normal to have a bugfix version instead?) One question: Have anyone apply Kafka 3.1 (not about cluster but about client) in stage/production and track the stability of the streaming queries? We are jumping from Kafka 2.8.0 to 3.1.0, one major and another minor. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
