HeartSaVioR commented on pull request #34089: URL: https://github.com/apache/spark/pull/34089#issuecomment-1034211081
> The client related changes with compatibility impact are changes in default (acks and idempotence), so people have full control over them via their client configuration. Could you please elaborating more on this? Does this mean Kafka 3.0 has different default values on functionality related configurations? If then it sounds like end users using Kafka 3.0 should understand what is going on before moving on, and the end users of Spark will have to do this in technically "minor version upgrade". -- 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]
