Github user squito commented on the pull request:
https://github.com/apache/spark/pull/3029#issuecomment-62475673
I was just about to suggest the same thing . So I admit it seemed a lot
cooler to have the console keep updating, but I agree with their concerns.
As a slight modification of @kayousterhout 's proposal, what if instead of
logging for *every* update, you log whenever some time unit have elapsed (eg.,
1 second) *and* some unit of work has been done (that is, both conditions must
be true, not either for either condition)? That way the logs dont' get
clobbered with lots of little updates -- if you have 1000 tasks but the whole
thing finishes in under 1 second, you really don't to monitor the progress in
the logs. But by just using the normal logging mechanism, its still
controllable via normal logging mechanism & plays nicely.
---
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
