Github user ajbozarth commented on the pull request:
https://github.com/apache/spark/pull/10405#issuecomment-166391481
@srowen I thought the same thing so I looked into git history and git blame
and found that this is how `updateTaskAccumulatorValues` has always worked,
it's original code up until the change in SPARK-11206 had a null check that
immediately returned at the start of the function.
---
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
