[
https://issues.apache.org/jira/browse/HIVE-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13674097#comment-13674097
]
Carl Steinbach commented on HIVE-4629:
--------------------------------------
Here are some questions I had while looking at the API:
* When am I allowed to call GetLog()? For example, what happens if I call it
after calling CloseOperation or CancelOperation? If it's ok to call after
CloseOperation()/CancelOperation(), what does it return, and what does it
return if I first call a function that also returns an operationhandle?
* What happens if I call GetLog() twice during the same operation? Will it
always return the entire log collected up to that point or just a piece of it?
* Do you think we log (or should log) anything of interest between the
OpenSession() call and creation of the first OperationHandle, or between
CloseSession() and the previous call to CancelOperation()/CloseOperation()?
I also thought of a possible alternate approach and wanted to get your opinion
on it:
* Provide access to logs on a per-session basis instead of per-operation.
* Provide a LogHandle (either hanging off of the SessionHandle or provided via
GetLogHandle()) and make it fetchable with FetchResults()
* We can provide per-operation log retrieval by supporting scrollable log
cursors, e.g. scrolling to FETCH_LAST between operations will advance the log
stream to the start of the next operation's log.
> 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
> Reporter: Shreepadma Venugopalan
> Assignee: Shreepadma Venugopalan
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
