You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Tao Li (JIRA)" <ji...@apache.org> on 2016/08/24 17:28:21 UTC

[jira] [Updated] (HIVE-14618) beeline fetch logging delays before query completion

     [ https://issues.apache.org/jira/browse/HIVE-14618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tao Li updated HIVE-14618:
--------------------------
    Description: 
Beeline has a thread that fetches logs from HS2. However, it uses the same HiveStatement object to also wait for query completion using a long-poll (with default interval of 5 seconds).
The jdbc client has a lock around the thrift api calls, resulting in the getLogs api blocking on the query completion check. ie the logs would get shown only every 5 seconds by default.
cc @Vaibhav Gumashta Gopal Vijayaraghavan Gunther Hagleitner

> beeline fetch logging delays before query completion
> ----------------------------------------------------
>
>                 Key: HIVE-14618
>                 URL: https://issues.apache.org/jira/browse/HIVE-14618
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Tao Li
>            Assignee: Tao Li
>
> Beeline has a thread that fetches logs from HS2. However, it uses the same HiveStatement object to also wait for query completion using a long-poll (with default interval of 5 seconds).
> The jdbc client has a lock around the thrift api calls, resulting in the getLogs api blocking on the query completion check. ie the logs would get shown only every 5 seconds by default.
> cc @Vaibhav Gumashta Gopal Vijayaraghavan Gunther Hagleitner



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)