Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/16537
Yeah, I thought this was the other PR that validates the function is
callable. Still, I don't agree that it's okay for python to be less friendly as
long as we don't think people will hit the problem too much or because they
solve the problem before asking a list. There are reasonable ways to hit this
and Spark should give a good explanation about what went wrong.
I'm not saying we have to go fix all of the cases like this, but where
there's a PR ready to go I think it's better to include it than not.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
