[
https://issues.apache.org/jira/browse/TAJO-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269797#comment-14269797
]
ASF GitHub Bot commented on TAJO-1282:
--------------------------------------
Github user hyunsik commented on the pull request:
https://github.com/apache/tajo/pull/334#issuecomment-69222736
I rebased and cleaned up the relationship. This patch does as follows:
* Remove CompisiteService from QueryInProgress
* Remove AsyncDispatcher from QueryInProgress
* Change QueryJobManager to handle all query-related events and routes them
to each QueryInProgress instance.
* Remove the following event types in QueryJobEvent:
* QUERY_JOB_START
* QUERY_JOB_FINISH
* QUERY_MASTER_START
* QUERY_MASTER_STOP
> 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
>
> Attachments: TAJO-1282.patch
>
>
> 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)
