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 2014/08/04 08:04:11 UTC
[jira] [Commented] (TAJO-985) Client API should be async
[ https://issues.apache.org/jira/browse/TAJO-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084334#comment-14084334 ]
ASF GitHub Bot commented on TAJO-985:
-------------------------------------
Github user hyunsik commented on a diff in the pull request:
https://github.com/apache/tajo/pull/99#discussion_r15741540
--- Diff: tajo-client/src/main/java/org/apache/tajo/cli/TajoCli.java ---
@@ -487,7 +487,7 @@ private void waitForQueryCompleted(QueryId queryId) {
while (true) {
// TODO - configurable
status = client.getQueryStatus(queryId);
- if(status.getState() == QueryState.QUERY_MASTER_INIT || status.getState() == QueryState.QUERY_MASTER_LAUNCHED) {
--- End diff --
The line is longer than 120 columns.
> Client API should be async
> --------------------------
>
> Key: TAJO-985
> URL: https://issues.apache.org/jira/browse/TAJO-985
> Project: Tajo
> Issue Type: Bug
> Components: query master
> Affects Versions: 0.9.0
> Reporter: Jinho Kim
> Assignee: Jinho Kim
>
> The query status synchronization on state machine always wait for time (event processing time) before status changes. If a lot of time are being processed to the event dispatcher, client api(getStatus, getProgress) will be waiting for changed event status. and query will be session timed out.
--
This message was sent by Atlassian JIRA
(v6.2#6252)