Mailing-List: contact dev-help@tajo.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tajo.incubator.apache.org
Date: Tue, 19 Nov 2013 05:45:21 +0000 (UTC)
From: "Hyunsik Choi (JIRA)" <jira@apache.org>
To: dev@tajo.incubator.apache.org
Message-ID: <JIRA.12679682.1384756374444.96369.1384839921376@arcas>
In-Reply-To: <JIRA.12679682.1384756374444@arcas>
References: <JIRA.12679682.1384756374444@arcas>
Subject: [jira] [Commented] (TAJO-314) Make TaskScheduler be pluggable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ 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)