HeartSaVioR commented on PR #49905: URL: https://github.com/apache/spark/pull/49905#issuecomment-2655107396
What I meant is, don't we just want to remove the config ASAP as I was under the impression like that in the previous discussion thread. If I was wrong, I feel like we were overreacted. We should have just filed a JIRA ticket marked as a blocker, and followed the full process. If I wasn't wrong, I believe this is the fastest way with very small impact. We change the config, release the new version, guiding users a way to mitigate if they are in combination of "starting query from 3.5.4, and upgrading to this version, and somehow hit some weird issue". This is just the same with what we were in Spark 3.5.3-. The whole effect is that they went back with the time whether there was no fix. -- 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]
