[
https://issues.apache.org/jira/browse/TAJO-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266385#comment-14266385
]
Hyunsik Choi commented on TAJO-1278:
------------------------------------
The main cause is as follows. So far, we have used the query state maintained
in QueryMaster. TAJO-1228 changes TajoClient to pass through only TajoMaster
instead of QueryMaster. TajoMaster has not maintained running as well as
finished query states. There are some synchronization issues and wrong
implementation. Most of them are caused by messy code.
So, instead of fixing only the problem itself, I'll create some refactoring and
clean issues to recap them and cleanup the relationship between QueryInProgress
and QueryJobManater.
> Unit tests occasionally hang due to the invalid query status
> ------------------------------------------------------------
>
> Key: TAJO-1278
> URL: https://issues.apache.org/jira/browse/TAJO-1278
> Project: Tajo
> Issue Type: Bug
> Components: test
> Reporter: Jihoon Son
> Assignee: Hyunsik Choi
> Priority: Blocker
> Fix For: 0.10
>
>
> See the title.
> Sometimes, even though a query is successfully finished during unit tests,
> its state is not QUERY_SUCCEEDED at QueryClientImpl. As a result, the query
> runs forever.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
