Github user pavel-sakun commented on the issue:
https://github.com/apache/spark/pull/19457
Not aware ATM, this one handles missing value for args expecting one.
---
-
To unsubscribe, e-mail: reviews-unsubscr
GitHub user pavel-sakun opened a pull request:
https://github.com/apache/spark/pull/19457
[SPARK] Misleading error message
Fix misleading error message when argument is expected.
## What changes were proposed in this pull request?
Change message to be accurate
Github user pavel-sakun closed the pull request at:
https://github.com/apache/spark/pull/5202
---
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
Github user pavel-sakun commented on the pull request:
https://github.com/apache/spark/pull/5202#issuecomment-86525129
Name usually tells something about the purpose of the object, so this
channel was most likely intended for writing error messages so they are not
mess with normal
Github user pavel-sakun commented on the pull request:
https://github.com/apache/spark/pull/5202#issuecomment-86491813
Isn't it why loggers/levels/categories and all that stuff exist? Stderr as
it's name implies should be used for error messages. In case of submitting jo
GitHub user pavel-sakun opened a pull request:
https://github.com/apache/spark/pull/5202
SPARK-6549 - Spark console logger logs to stderr by default
Changed default log4j configuration to log into stdout by default
You can merge this pull request into a Git repository by running
