HeartSaVioR commented on PR #55410: URL: https://github.com/apache/spark/pull/55410#issuecomment-5925992946
Sorry for back and forth, I hit the enter button too soon. The case we describe in migration guide is actually a behavior change from fixing the bug on Spark Connect, and it doesn't seem to be a valid pattern (even for Spark Classic). Maybe the baseline can be set to Spark Classic; if it doesn't work in Spark Classic, it's definitely no-go. If it works in Spark Classic but it's "expected" to not work in Spark Connect (due to technical issue e.g. serialization), it's also no-go. Otherwise I think we need to try fixing it. Maybe I could spend some time to validate my comment by myself. My apologize for the incomplete feedback. -- 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]
