GitHub user michaelmior opened a pull request: https://github.com/apache/spark/pull/19263
Optionally add block updates to log I see that block updates are not logged to the event log. This makes sense as a default for performance reasons. However, I find it helpful when trying to get a better understanding of caching for a job to be able to log these updates. This PR adds a configuration setting `spark.eventLog.blockUpdates` (defaulting to false) which allows block updates to be recorded in the log. You can merge this pull request into a Git repository by running: $ git pull https://github.com/michaelmior/spark log-block-updates Alternatively you can review and apply these changes as the patch at: https://github.com/apache/spark/pull/19263.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #19263 ---- commit 2a967c368cf72316b760c5f17503658aa12b901d Author: Michael Mior <mm...@uwaterloo.ca> Date: 2017-07-12T13:32:24Z Optionally add block updates to log ---- --- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org