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

Hitesh Shah commented on AMBARI-14951:
--------------------------------------

[~sumitmohanty] please review. Reactor order seems to be fine on my local 
setup: 

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Ambari Contrib Views
[INFO] Ambari View Utils
[INFO] Files
[INFO] Jobs
[INFO] Pig
[INFO] Slider
[INFO] Capacity Scheduler
[INFO] Tez
[INFO] Storm_Monitoring
[INFO] Hive
[INFO]

> Tez Ambari View: Add protocol configuration for YARN
> ----------------------------------------------------
>
>                 Key: AMBARI-14951
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14951
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.2.2
>            Reporter: Sreenath Somarajapuram
>            Assignee: Sreenath Somarajapuram
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-14951.1.patch, AMBARI-14951.2.patch, 
> AMBARI-14951.3.patch
>
>
> - Value set in yarn.http.policy is required for creating task attempt log 
> links, and we need a mechanism to get that configuration value at the UI side.
> - As host points to Ambari proxy, there is no way to know the protocol at 
> which yarn daemons are configured to run. 



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

Reply via email to