Github user squito commented on the pull request:
https://github.com/apache/spark/pull/3029#issuecomment-62499404
I totally see the appeal of the one-progress bar (hence my initial
excitement when I tried this out). But if it doesn't play nicely with logging
& multiple stages, this seems like a very small improvement for the initial
user experience, but a big headache for serious users.
I don't think its really that much worse if your example changes to
```
scala> rdd.count()
[INFO] Stage 1 [=> ]
[INFO] Stage 1 [==========> ]
[INFO] Stage 1 finished in 2 seconds (med/avg/xxxx)
res0: Int = xxxx
```
In this case its just a couple more lines. If the stage took longer, than
it would be even more lines, but that seems ok, since its not that much noise
per unit time.
If the code were moved to a separate SparkListener implementation, than it
could have its own log level, and even be INFO by default (so we leave
everything else as WARN). INFO for everything in spark is way too noisy for
the average spark user, but that doesn't mean we can't use INFO for a few
select classes.
---
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]
