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

Lefty Leverenz commented on HIVE-4629:
--------------------------------------

Does this need to be documented in the wiki?

Of course, two new parameters need to go in Configuration Properties 
(*hive.server2.logging.operation.enabled*, 
*hive.server2.logging.operation.log.location*), but should general guidance be 
given in one of the HS2 wikidocs?  The logging section in Getting Started could 
also mention this.

* [HiveServer2 Clients | 
https://cwiki.apache.org/confluence/display/Hive/HiveServer2+Clients]
* [Setting Up HiveServer2 | 
https://cwiki.apache.org/confluence/display/Hive/Setting+Up+HiveServer2]
* [Getting Started -- Error Logs | 
https://cwiki.apache.org/confluence/display/Hive/GettingStarted#GettingStarted-ErrorLogs]
* [Configuration Properties -- HiveServer2 | 
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-HiveServer2]



> 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
>              Labels: TODOC14
>             Fix For: 0.14.0
>
>         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, HIVE-4629.8.patch, 
> HIVE-4629.9.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)

Reply via email to