vrozov commented on PR #52484: URL: https://github.com/apache/spark/pull/52484#issuecomment-3354052340
Is it possible that `BreakingChange` will require more than one `MitigationConfig`? While currently there is one to one mapping, in the future can it require more than one? Also, should `MitigationConfig` be inner class of `BreakingChangeInfo`? Are there any use case for `MitigationConfig` that is not part of `BreakingChangeInfo`? -- 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]
