Github user davies commented on the pull request:
https://github.com/apache/spark/pull/1776#issuecomment-51543727
Before moving on, maybe the first question is that, does Spark 1.1 is so
stable that we can trust it work as expected? If yes in most cases, I think
reduce the chatty loggings will make sense. If not, then we should continue
with that and revisit in the future.
If user has some problems, she will try to ru-run the program several times
to make sure that the problem is re-producable. During these, turning on DEBUG
loggings will be reasonable. It will more helpful if she could switch the
logging on/off by single argument, such as "-v" or "-q".
In current code base, most of the loggings happens in normal code path,
they show what exactly happen right now. They are useful for developer to
troubleshoot, but just be noisy to user. User should be focus on her business
login, not the details of spark.
We will not remove these loggings, just want to hidden them to users by
default, only keep the really useful loggings, such as address of web UI, and
progress loggings (replaces by other cool stuff will be better).
---
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]
