ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-11516) Views : Add URLConnectionProvider interface
Date Fri, 29 May 2015 04:06:17 GMT

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

Hudson commented on AMBARI-11516:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #2742 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2742/])
AMBARI-11516 - Views : Add URLConnectionProvider interface (tbeerbower) (tbeerbower: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6c0f9acef0f7ada38ebbd59a4fc2a70652050f4c)
* ambari-server/src/main/java/org/apache/ambari/server/view/ViewURLStreamProvider.java
* ambari-views/pom.xml
* ambari-server/src/test/java/org/apache/ambari/server/view/ViewURLStreamProviderTest.java
* ambari-views/src/main/java/org/apache/ambari/view/ViewContext.java
* ambari-views/src/main/java/org/apache/ambari/view/URLConnectionProvider.java
* ambari-server/src/test/java/org/apache/ambari/server/view/ViewContextImplTest.java
* ambari-server/src/main/java/org/apache/ambari/server/view/ViewContextImpl.java


> Views : Add URLConnectionProvider interface
> -------------------------------------------
>
>                 Key: AMBARI-11516
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11516
>             Project: Ambari
>          Issue Type: Task
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>             Fix For: 2.1.0
>
>
> Make an enhancement to view framework to expose a connection provider interface and make
it available through the view context. This is being requested because the existing URLStreamProvider
interface can only return a stream and does not provide any http error code or response body
on failures.
> Requested for TEZ view ...
> {quote}
> The lack of this functionality makes it next to impossible to debug why a view is not
working.
> The tez view has hacks to reduce the message body for potential errors or treat an empty
body as a 404.
> For security errors, invalid hostnames/connection end points, etc. - instead of getting
401s/403s/connection timeouts/..., the UI ends up always showing a 404.
> {quote}



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

Mime
View raw message