You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/01/06 18:08:35 UTC

[jira] [Commented] (TAJO-1282) Cleanup the relationship of QueryInProgress and QueryJobManager

    [ https://issues.apache.org/jira/browse/TAJO-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266413#comment-14266413 ] 

ASF GitHub Bot commented on TAJO-1282:
--------------------------------------

GitHub user hyunsik opened a pull request:

    https://github.com/apache/tajo/pull/334

    TAJO-1282: Cleanup the relationship of QueryInProgress and QueryJobManager.

    It's initial work.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/hyunsik/tajo TAJO-1282

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/tajo/pull/334.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #334
    
----
commit 57e561bc6789b395bda8848583593b3d0f20ec62
Author: Hyunsik Choi <hy...@apache.org>
Date:   2015-01-06T17:03:33Z

    Remove TajoMasterService::stopQueryMaster API call.

----


> Cleanup the relationship of QueryInProgress and QueryJobManager
> ---------------------------------------------------------------
>
>                 Key: TAJO-1282
>                 URL: https://issues.apache.org/jira/browse/TAJO-1282
>             Project: Tajo
>          Issue Type: Improvement
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>             Fix For: 0.10
>
>
> Each QueryInProgress instance maintains an individual event handler involving each thread. It complicates the relationship between QueryJobManager and QueryInprogress. The main objective of this issue is to remove each event handler from QueryInProgress and distinguishes their roles of both classes.



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