Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/16537
I don't think it is a good idea to think that this has little use because
it is a dumb mistake to pass something that isn't callable. In this case, it's
easy to accidentally reuse a name for a function and a variable (e.g.,
`format`), especially as scripts change over time and pass from one maintainer
to another.
Spark should have reasonable behavior for any error, as opposed to being
harder to work with because we thought the user wasn't likely to hit a
particular problem. This is very few lines of code that will make a user's
experience much better because it can catch exactly what the problem is,
without running a job.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
