ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sreenath Somarajapuram (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-14940) Tez Ambari View: Improve host & protocol configuration logic
Date Sat, 06 Feb 2016 16:41:39 GMT

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

Sreenath Somarajapuram updated AMBARI-14940:
--------------------------------------------
    Description: - Currently host for rm and timeline is obtained from window.location.origin.
As the support for origin is limited to modern browsers its better to construct the value
from location.protocol, location.hostName & location.port.  (was: - Currently host for
rm and timeline is obtained from window.location.origin. As the support for origin is limited
to modern browsers its better to construct the value from location.protocol, location.hostName
& location.port.
- As host points to Ambari proxy, there is no way to know the protocol at which yarn daemons
are configured to run. 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.
)

> Tez Ambari View: Improve host & protocol configuration logic
> ------------------------------------------------------------
>
>                 Key: AMBARI-14940
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14940
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Sreenath Somarajapuram
>            Assignee: Sreenath Somarajapuram
>
> - Currently host for rm and timeline is obtained from window.location.origin. As the
support for origin is limited to modern browsers its better to construct the value from location.protocol,
location.hostName & location.port.



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

Mime
View raw message