[jira] [Commented] (KNOX-2354) Add minimal service for proxying HBase artifacts from WebUI

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on KNOX-2354:
-------------------------------------------------------

Commit bbcaaff1d3483d706f7d76c344920b4f755809b7 in knox's branch refs/heads/master from Josh Elser
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=bbcaaff ]

KNOX-2354 An HBASEJARS service which can proxy HBase jars hosted by t… (#325)

* KNOX-2354 An HBASEJARS service which can proxy HBase jars hosted by the HBASEUI

In HBase, we can host a "mini" maven repo in hbase itself which a maven
application can point to.

We want this to be in its own service because it has different semantics
than the normal hbaseUI service has (e.g. one would be hooked up to SSO
login, but SSO won't work against that), and Maven cannot function with
the query-string based backend-routing that we do to make the HBaseUI
look like a normal website (instead of a collection of independent
webservers).

* Add some context as to why this custom dispatch is here.

> Add minimal service for proxying HBase artifacts from WebUI
> -----------------------------------------------------------
>
>                 Key: KNOX-2354
>                 URL: https://issues.apache.org/jira/browse/KNOX-2354
>             Project: Apache Knox
>          Issue Type: Improvement
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Major
>             Fix For: 1.4.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The normal HBASEUI service is intended to be used for proxying the HBASEUI. However, we can also support fetching of static resources from the HBase UI to enable some interesting developer-enablement use cases.
> However, we would intend the fetching of these resources to be done programmatically (with username/password credentials) whereas we would expect the HBASEUI to be accessed behind an SSO provider (with a user at their web browser).
> The easiest thing to do here would be to create a very minimal service which can hit the hbase UI, pull these resources, and be tied up to a topology (separate from where HBASEUI is exposed)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)