sarutak edited a comment on pull request #31569: URL: https://github.com/apache/spark/pull/31569#issuecomment-821086061
> Backing up - this change isn't about removing usage of Symbol, but a deprecated syntax for Symbol. This doesn't actually change anything but how it's expressed in source code right? if so, why not do this in Spark (aside from the large code churn of course)? I intended to just replace symbol literal with `Symbol` constructor invocation but I found `Symbol` is deprecated in the future. https://github.com/apache/spark/pull/31569#issuecomment-781220980 If the decision will not be changed, we need to remove the usage of symbols right? (If so, the title of this PR needs do be changed) > Changing to Column syntax is another question. Yeah, at first, the syntax stuff is a separate one but after a discussion, the most part of the symbol usage was to be removed. https://github.com/apache/spark/pull/31601#discussion_r581968701 -- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
