[
https://issues.apache.org/jira/browse/TAJO-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13826219#comment-13826219
]
Hyunsik Choi commented on TAJO-314:
-----------------------------------
The main reason why the storage manager uses handler names and a map to
indicate an actual class name is to enable users to not specify very long
canonical class names within a SQL statement. However, for scheduler, I think
that just a class name may be enough. Also, I would like to suggest
'tajo.querymaster.task-scheduler.class' because TaskScheduler works in
querymaster.
I'll continue to review the remain parts.
> 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)
