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

Hudson commented on AMBARI-14951:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #4409 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4409/])
AMBARI-14951. Tez Ambari View: Add protocol configuration for YARN. (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4cd5ad4e61c2a9a3cfc7e22233b484e8fc88e8b2])
* contrib/views/tez/src/main/java/org/apache/ambari/view/tez/ViewController.java
* contrib/views/hive/pom.xml
* contrib/views/utils/pom.xml
* contrib/views/pom.xml
* contrib/views/files/pom.xml
* 
contrib/views/utils/src/test/java/org/apache/ambari/view/utils/ambari/ServicesTest.java
* contrib/views/tez/pom.xml
* 
contrib/views/tez/src/main/java/org/apache/ambari/view/tez/ViewControllerImpl.java
* contrib/views/pig/pom.xml
* 
contrib/views/utils/src/main/java/org/apache/ambari/view/utils/ambari/Services.java
* contrib/views/slider/pom.xml
* contrib/views/tez/src/main/resources/ui/scripts/init-ambari-view.js
* contrib/views/capacity-scheduler/pom.xml


> 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, AMBARI-14951.4.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