[
https://issues.apache.org/jira/browse/TEZ-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Zhang updated TEZ-1218:
----------------------------
Attachment: Tez_1218.patch
attache the patch.
Several changes:
* Rename TaskSchedulerInterface to TaskSchedulerService and extends
AbstractService
* Rename LocalTaskScheduler to LocalTaskSchedulerSerivce , rename TaskScheduler
to YarnTaskSchedulerService
* Move TaskSchedulerAppCallback from TaskScheduler to TaskSchedulerService
> Make TaskScheduler as AbstractService rather than just an interface
> -------------------------------------------------------------------
>
> Key: TEZ-1218
> URL: https://issues.apache.org/jira/browse/TEZ-1218
> Project: Apache Tez
> Issue Type: Improvement
> Affects Versions: 0.4.0
> Reporter: Jeff Zhang
> Assignee: Jeff Zhang
> Attachments: Tez_1218.patch
>
>
> Currently, the TaskSchedulerInterface is just a interface. And in
> TaskSchedulerEventHandler we explicitly convert it to AbstractService to init
> and start it. This is not necessary, we could just make it as Service which
> is a very common pattern that EventHandler depends on Service just as we did
> in HistoryEventHandler that it depends on HistoryLoggingService.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
