Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 24 Aug 2016 19:13:21 +0000 (UTC)
From: "Tao Li (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.12999730.1472059597000.400438.1472066001727@Atlassian.JIRA>
In-Reply-To: <JIRA.12999730.1472059597000@Atlassian.JIRA>
References: <JIRA.12999730.1472059597000@Atlassian.JIRA> <JIRA.12999730.1472059597898@arcas>
Subject: [jira] [Updated] (HIVE-14618) beeline fetch logging delays before
 query completion
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 24 Aug 2016 19:13:23 -0000


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

Tao Li updated HIVE-14618:
--------------------------
    Attachment:     (was: HIVE-14618.1.patch)

> 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 [~vgumashta] [~gopalv] [~thejas]


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