Then I guess we're just a we service then ;)

On Friday, July 17, 2015, Adam Bordelon <[email protected]> wrote:

> Ken, Swapnil is looking at turning the executor into a YARN NM AuxService
> anyway, so it might end up without a main too. Then we wouldn't need the
> application plugin at all?
>
> On Fri, Jul 17, 2015 at 3:31 PM, Ken Sipe <[email protected]
> <javascript:;>> wrote:
>
> > Hey Patrick,
> >
> > I was the one that refactored myriad in to a multi-project structure.   I
> > took what was originally there and tried to maintain the semantics into
> the
> > new structure (meaning it was my intention to not change anything other
> > than the structure).  At first glance this appears to be a miss on my
> > part.   There is no main class in the scheduler.  The scheduler is a YARN
> > resource manager.
> >
> > Looking it over in more detail, I’m not sure we even need the application
> > plugin for the executor.  It is required for the building of the capsule,
> > but that could be declared in the capsule instead of using the
> > configuration of the application.  It is worth more investigation.
> >
> > As for long, there are no other projects other than the executor that
> need
> > the application plugin.  I have refactored this and have submitted it as
> > PR-120:  https://github.com/mesos/myriad/pull/120 <
> > https://github.com/mesos/myriad/pull/120>
> >
> > Thanks for helping to identify this.
> >
> > Ken
> >
> > > On Jul 17, 2015, at 3:50 PM, Patrick Wong <[email protected]
> <javascript:;>> wrote:
> > >
> > > Hello Myriad Team,
> > >
> > > I noticed that the application plugin is applied to all subprojects.
> Does
> > > this mean that you are supposed to be able to run "gradle installDist"
> to
> > > get a working local installation for each subproject, and "gradle run"
> to
> > > run them?
> > >
> > > --
> > > Patrick Wong
> > > 510.386.7205
> > >
> > > mapr.com
> >
> >
>

Reply via email to