[
https://issues.apache.org/jira/browse/SPARK-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15578914#comment-15578914
]
Lars Francke commented on SPARK-650:
------------------------------------
I can only come up with three reasons at the moment. I hope they all make sense.
1) Singletons/Static Initialisers run once per Class Loader where this class is
being loaded/used. I haven't actually seen this being a problem (and it might
actually be desired behaviour in this case) but making the init step explicit
would prevent this from ever becoming one.
2) I'd like to fail fast for some things and not upon first access (which might
be behind a conditional somewhere)
3) It is hard enough to reason about where some piece of code is running as it
is (Driver or Task/Executor), adding Singletons to the mix makes it even more
confusing.
> Add a "setup hook" API for running initialization code on each executor
> -----------------------------------------------------------------------
>
> Key: SPARK-650
> URL: https://issues.apache.org/jira/browse/SPARK-650
> Project: Spark
> Issue Type: New Feature
> Components: Spark Core
> Reporter: Matei Zaharia
> Priority: Minor
>
> Would be useful to configure things like reporting libraries
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
