I get it, the use case here sounds like adding some logic that's not
specific to an app. Adding to every job of every app would be painful then.
Any task can make sure the init has happened, so doesn't matter if later
tasks execute elsewhere. But if the desired init is really for all tasks,
or
The issue is: where do you name the class you want to initialize? In your job?
What if the plugin has nothing to do with your job, e.g. it's some
monitoring tool? Are you going to modify all your jobs so you include
initialization of that particular plugin? Forcing everybody to change
their code,
+1
Class init is not enough because there is nowhere for you to force a
random class to be initialized. This is basically adding that
mechanism, instead of forcing people to add hacks using e.g.
mapPartitions which don't even cover all scenarios.
On Tue, Aug 28, 2018 at 7:09 AM, Sean Owen
Still +0 on the idea, as I am still not sure it does much over simple JVM
mechanisms like a class init. More comments on the JIRA. I can't say it's a
bad idea though, so would not object to it.
On Tue, Aug 28, 2018 at 8:50 AM Imran Rashid
wrote:
> There has been discussion on jira & the PR, all
+1
Tom
On Tue, Aug 28, 2018 at 8:50 AM Imran Rashid
wrote:
> There has been discussion on jira & the PR, all generally positive, so I'd
> like to call a vote for this spip.
>
> I'll start with own +1.
>
> On Fri, Aug 3, 2018 at 11:59 AM Imran Rashid wrote:
>
>> I'd like to propose adding a
There has been discussion on jira & the PR, all generally positive, so I'd
like to call a vote for this spip.
I'll start with own +1.
On Fri, Aug 3, 2018 at 11:59 AM Imran Rashid wrote:
> I'd like to propose adding a plugin api for Executors, primarily for
> instrumentation and debugging (
>
