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

Posted to dev@lens.apache.org by "Rajat Khandelwal (JIRA)" <ji...@apache.org> on 2016/03/15 10:00:43 UTC

[jira] [Assigned] (LENS-664) Fetch driver execution logs

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

Rajat Khandelwal reassigned LENS-664:
-------------------------------------

    Assignee: Rajat Khandelwal

> Fetch driver execution logs
> ---------------------------
>
>                 Key: LENS-664
>                 URL: https://issues.apache.org/jira/browse/LENS-664
>             Project: Apache Lens
>          Issue Type: Improvement
>          Components: driver-hive
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Rajat Khandelwal
>
> HiveServer2 can give driver execution logs through thrift api for any operation - available through HIVE-4629.
> This issue is to fetch the logs from HiveServer2 and log them in lens query log segregation context. This user will be able to see the underlying logs from hive for query execution as well.
> This should also publish the overhead getting added on query or HiveServe2, if log fetching is enabled. And if the overhead is significant, user should be able turn off log fetching per query.



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