You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Gopal V (JIRA)" <ji...@apache.org> on 2016/09/02 01:23:20 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 ]

Gopal V updated HIVE-14618:
---------------------------
       Resolution: Fixed
    Fix Version/s: 2.2.0
     Release Note: 
beeline fetch logging delays before query completion (Tao Li, via Gopal V)

           Status: Resolved  (was: Patch Available)

> 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
>             Fix For: 2.2.0
>
>         Attachments: HIVE-14618.1.patch, HIVE-14618.2.patch, HIVE-14618.3.patch
>
>
> 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 [~vgumashta] [~gopalv] [~thejas]



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