[
https://issues.apache.org/jira/browse/KNOX-2376?focusedWorklogId=441024&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-441024
]
ASF GitHub Bot logged work on KNOX-2376:
----------------------------------------
Author: ASF GitHub Bot
Created on: 03/Jun/20 23:22
Start Date: 03/Jun/20 23:22
Worklog Time Spent: 10m
Work Description: joshelser opened a new pull request #338:
URL: https://github.com/apache/knox/pull/338
…hbase/maven
## What changes were proposed in this pull request?
Looks like I was getting turned around the first time, confusing what is
an internal path (HBase UI) and what is an external path (Knox gateway path).
This fixes the service such that we're always coming in to Knox at
/hbase/jars
and always going "out" (to hbase ui) as /static/maven.
Further, because we expect this to be deployed as an API (rather than a
UI), we can do away with the rules to render the quirky jetty-dir.css.
(It is very **important** that you created an Apache Knox JIRA for this
change and that the PR title/commit message includes the Apache Knox JIRA ID!)
## How was this patch tested?
Modified a Knox installation that has this set up, touched the topology and
restarted the gateway to ensure it was redeployed. Validated that a maven
application could pull the jar(s) required through Knox.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 441024)
Remaining Estimate: 0h
Time Spent: 10m
> Correct confusing HBASEJARS service
> -----------------------------------
>
> Key: KNOX-2376
> URL: https://issues.apache.org/jira/browse/KNOX-2376
> Project: Apache Knox
> Issue Type: Bug
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> HBASEJARS was a service that I added a while back to help with statically
> hosting jars from the HBase UI. The expectation was to serve this at
> "/hbase/jars" to match the name of the service itself. However, it looks like
> this got turned around with the confusion in what it looks like from the
> HBase POV.
> Simple change incoming to try to make this less confusing for the next person.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
