[
https://issues.apache.org/jira/browse/AMBARI-11516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Beerbower updated AMBARI-11516:
-----------------------------------
Description:
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}
was:
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 ...
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.
> 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)
