[
https://issues.apache.org/jira/browse/TAJO-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13826278#comment-13826278
]
Jihoon Son commented on TAJO-314:
---------------------------------
Or, we can consider adding an abstract newTaskSchedulerEvent() function to the
AbstractTaskScheduler class like this.
{code}
public abstract class AbstractTaskScheduler extends AbstractService
implements EventHandler<TaskSchedulerEvent> {
/**
* Construct the service.
*
* @param name service name
*/
public AbstractTaskScheduler(String name) {
super(name);
}
public abstract void handleTaskRequestEvent(TaskRequestEvent event);
public abstract TaskSchedulerEvent newTaskSchedulerEvent(EventType type,
QueryUnitAttempt queryUnitAttempt);
}
{code}
> Make TaskScheduler be pluggable
> -------------------------------
>
> Key: TAJO-314
> URL: https://issues.apache.org/jira/browse/TAJO-314
> Project: Tajo
> Issue Type: Improvement
> Components: master
> Reporter: Jihoon Son
> Assignee: Jihoon Son
> Fix For: 0.8-incubating
>
> Attachments: TAJO-314.patch
>
>
> The task scheduler can be changed according to the task scheduling algorithm,
> the locality policy of the storage, and so on.
> Thus, we need to improve the task scheduler interface to be pluggable.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
