[
https://issues.apache.org/jira/browse/TAJO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyunsik Choi updated TAJO-706:
------------------------------
Attachment: TAJO-706_3.patch
I'm sorry for the late review.
I just added some comments and timeout annotation in the patch. I believe that
the comments make the changes more comprehensive.
Also, in my opinion, the patch looks good to me. The main problem is that the
finished query status cannot be obtained from getQueryStatus(). The patch
exactly fixes the problem. I think that the unit test verifies the case well.
Here is my +1.
As far as I know, Jihoon has faced this problem in his application. So, his
real test would be helpful to ensure that this change correctly fixes the
problem.
> In the case of very quick query, client can't get query status.
> ---------------------------------------------------------------
>
> Key: TAJO-706
> URL: https://issues.apache.org/jira/browse/TAJO-706
> Project: Tajo
> Issue Type: Bug
> Reporter: hyoungjunkim
> Assignee: hyoungjunkim
> Priority: Minor
> Attachments: TAJO-706.patch, TAJO-706_2.patch, TAJO-706_3.patch
>
>
> See the title. TajoClient calls getQueryStatus() to TajoMaster or QueryMaster
> every 500ms. If a query is ended within 500ms, TajoClient can't get query
> status from TajoMaster. The cause of this problem is that TajoMaster get a
> status from QueryInProgress.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
