My change in stance partially came from the realization that the scheduler is not currently coupled to the executor implementation. As a result, an API consumer (bypassing the client) could already use any executor implementation they choose. This could be interpreted as custom executor support, and i would like to know if that satisfies the general use case.
I am slightly uneasy about supporting user-selected executors on the scheduler simply because of the complexity that comes with it (the configuration complexity is one, but there will also likely be a need for ACLs, and even greater complexity in the client to support multiple/arbitrary configuration input formats). So, my question becomes - is this (end-user-selected executors) a real use case today, or a hypothetical one? If it a real use case, some elaboration would be useful to make sure we are building the right software for it. On Tue, Nov 3, 2015 at 9:30 PM, <meghdoo...@yahoo.com> wrote: > Bill what do you think? > > Thx > > Sent from my iPhone > > > On Nov 2, 2015, at 1:00 PM, Zameer Manji <zma...@apache.org> wrote: > > > > +wfarner > > > > I believe Bill was heavily involved in reviewing the proposed patch and > > design. Bill, care to comment on what you think here? > > > >> On Mon, Nov 2, 2015 at 12:55 PM, <meghdoo...@yahoo.com.invalid> wrote: > >> > >> Do we have a decision on this? > >> > >> https://issues.apache.org/jira/plugins/servlet/mobile#issue/AURORA-1376 > >> > >> It would help to know where we stand on this. > >> > >> Thx > >> > >> > >> Sent from my iPhone > >> > >> -- > >> Zameer Manji > >> > >> >
