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

Sreenath Somarajapuram commented on TEZ-3086:
---------------------------------------------

[~hitesh]
The current approaches:

Query display:
- The UI looks for the query string inside 
otherinfo.dagPlan.dagInfo.description OR otherinfo.dagPlan.dagInfo.blob OR 
otherinfo.dagPlan.dagContext.description. Will deserialize dagInfo JSON if 
required.
- * If none of the above is available, then we presume the caller to be hive 
and try hitting HIVE_QUERY_ID. As the callerId is not available, we try to 
create it form dagName (We cut out every text before the first ":"). 
- * If the server returns expected data, then we assume the callerType to be 
Hive and display the string in otherinfo.QUERY.queryText.

Progress:
- Until now we were just using Tez Web Service version 2, this change is to use 
version 1 also. It provides progress into for DAGs and Vertices.
- In TEZ_DAG_ID, otherinfo.amWebServiceVersion says the maximum version thats 
supported. If value is not present it means the version is 1.
- So if v1: We change the end points that we hit as follows
-- Instead of <address>:8088/proxy/<app_id>/ws/v2/tez/dagInfo we hit 
<address:>8088/proxy/<app_id>/ws/v1/tez/dagProgress
-- And instead of <address>:8088/proxy/<app_id>/ws/v2/tez/vertexInfo we hit 
<address:>8088/proxy/<app_id>/ws/v1/tez/vertexProgresses

> Tez UI 2: Backward compatibility changes
> ----------------------------------------
>
>                 Key: TEZ-3086
>                 URL: https://issues.apache.org/jira/browse/TEZ-3086
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Sreenath Somarajapuram
>            Assignee: Sreenath Somarajapuram
>         Attachments: TEZ-3086.1.patch, TEZ-3086.2.patch
>
>
> -Caller info is displayed for old dagInfo format-
> - Utilize DAG & Vertex progress value provided by AM web service V1
> - If not dagInfo, load caller tInfo from HIVE_QUERY_ID, and if available set 
> the caller type as Hive.



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

Reply via email to