You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2015/09/04 04:15:46 UTC

[jira] [Updated] (TAJO-1292) Separate TajoMaster role into three subcomponent

     [ https://issues.apache.org/jira/browse/TAJO-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyunsik Choi updated TAJO-1292:
-------------------------------
    Fix Version/s:     (was: 0.11.0)
                   0.12.0

> Separate TajoMaster role into three subcomponent
> ------------------------------------------------
>
>                 Key: TAJO-1292
>                 URL: https://issues.apache.org/jira/browse/TAJO-1292
>             Project: Tajo
>          Issue Type: Improvement
>          Components: TajoMaster
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>             Fix For: 0.12.0
>
>
> TajoMaster has various roles: query coordinator, resource manager, and client  API service. Please see TajoMaster section in https://cwiki.apache.org/confluence/display/TAJO/Tajo+Internal.
> But, the current implementation does not have any bound for these roles. So, the code readability is not good and some part is too messy. So, I'm going to explicitly separate these roles into packages and improve their cohesion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)