HeartSaVioR commented on pull request #34089: URL: https://github.com/apache/spark/pull/34089#issuecomment-1034365844
I don't think this is the right process. I shouldn't be someone who needs to prove the possible risks on other's proposal. If someone introduces the change, it's up to someone to explain the benefits and risks, and persuade about the change to the community despite the possible risks. I (as a committer) could ask, and reject the proposal if it doesn't make sense. What I have been figured out must be done in prior to merge this. Does it make sense? That said, I can initiate the discussion thread, but if I do, it's on behalf of authors and approvers on this PR. Not a duty of myself. -- 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]
