Github user srowen commented on the issue:

    https://github.com/apache/spark/pull/13842
  
    Well, it simplifies the code too and avoids a method call. The current 
variable really ought to be volatile but isn't, so I don't know if that's a 
downside. I think the performance issue is negligible, since the cost of 
dereferencing a volatile variable is nothing compared to the time to construct 
and log the message to disk. It's really minor but I think there are only 
upsides here.


---
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]

Reply via email to