Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Thu, 21 Aug 2014 23:42:12 +0000 (UTC)
From: "Brock Noland (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12650031.1369865651591.7692.1408664532989@arcas>
In-Reply-To: <JIRA.12650031.1369865651591@arcas>
References: <JIRA.12650031.1369865651591@arcas>
Subject: [jira] [Commented] (HIVE-4629) HS2 should support an API to
 retrieve query logs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HIVE-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106168#comment-14106168 ] 

Brock Noland commented on HIVE-4629:
------------------------------------

bq. I didn't see this in the patch. Are you referring to something in the Thrift IDL file or something else?

You are right...I was confused between ICLIService and TCLIService. The patch only adds a new option member to TFetchResultsReq which is exactly what I wanted.

Nevermind me :)

> HS2 should support an API to retrieve query logs
> ------------------------------------------------
>
>                 Key: HIVE-4629
>                 URL: https://issues.apache.org/jira/browse/HIVE-4629
>             Project: Hive
>          Issue Type: Sub-task
>          Components: HiveServer2
>            Reporter: Shreepadma Venugopalan
>            Assignee: Dong Chen
>         Attachments: HIVE-4629-no_thrift.1.patch, HIVE-4629.1.patch, HIVE-4629.2.patch, HIVE-4629.3.patch.txt, HIVE-4629.4.patch, HIVE-4629.5.patch, HIVE-4629.6.patch, HIVE-4629.7.patch
>
>
> HiveServer2 should support an API to retrieve query logs. This is particularly relevant because HiveServer2 supports async execution but doesn't provide a way to report progress. Providing an API to retrieve query logs will help report progress to the client.


--
This message was sent by Atlassian JIRA
(v6.2#6252)