hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <j...@apache.org>
Subject [jira] [Work logged] (HIVE-23972) Add external client ID to LLAP external client
Date Sat, 01 Aug 2020 01:38:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-23972?focusedWorklogId=465240&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-465240
]

ASF GitHub Bot logged work on HIVE-23972:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/Aug/20 01:37
            Start Date: 01/Aug/20 01:37
    Worklog Time Spent: 10m 
      Work Description: prasanthj commented on pull request #1350:
URL: https://github.com/apache/hive/pull/1350#issuecomment-667448124


   @jdere we already have a hive config hive.query.name. IIRC this query name will be converted
to DAG name and the llap proto schema should have a field for DAG name. Will that be sufficient
for this use case?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 465240)
    Time Spent: 20m  (was: 10m)

> Add external client ID to LLAP external client
> ----------------------------------------------
>
>                 Key: HIVE-23972
>                 URL: https://issues.apache.org/jira/browse/HIVE-23972
>             Project: Hive
>          Issue Type: Bug
>          Components: llap
>            Reporter: Jason Dere
>            Assignee: Jason Dere
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> There currently is not a good way to tell which currently running LLAP tasks are from
external LLAP clients, and also no good way to know which application is submitting these
external LLAP requests.
> One possible solution for this is to add an option for the external LLAP client to pass
in an external client ID, which can get logged by HiveServer2 during the getSplits request,
as well as displayed from the LLAP executorsStatus.
> cc [~ShubhamChaurasia]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message