[
https://issues.apache.org/jira/browse/TAJO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947485#comment-13947485
]
Jihoon Son commented on TAJO-706:
---------------------------------
[~hjkim], sorry for burdening you, but I have one more suggestion.
Nowadays, I'm designing a program using TajoClient. To get the query result, I
adopt the exactly same way with TajoCli, but, sometimes,
TajoClient.getResultResponse() doesn't work with emitting the following message.
{noformat}
2014-03-26 11:25:07,839 WARN client.TajoClient
(TajoClient.java:getResultResponse(296)) - No Connection to QueryMaster for
q_1395800666626_0001
{noformat}
I think that this problem is also caused by the request to the halted query
master.
However, many applications generally require to get query results even after
the query is finished, and, in my opinion, we should support it.
I think that this problem can be easily handled by the same way in your patch.
Would you add this feature in the next patch, please?
Thanks,
Jihoon
> 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
>
>
> 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)
