[
https://issues.apache.org/jira/browse/KNOX-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17791635#comment-17791635
]
ASF subversion and git services commented on KNOX-2675:
-------------------------------------------------------
Commit 7ee5c8c0dff655a426252da0a45bb2206b6eccaa in knox's branch
refs/heads/master from Denes Bodo
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=7ee5c8c0d ]
KNOX-2991 - Sanitise Oozie rewrite rules (#824)
* KNOX-2675 Oozie Console URL on the web UI should be a Knox URL
* KNOX-2991 - Sanitise Oozie rewrite rules
---------
Co-authored-by: Denes Bodo <[email protected]>
> Oozie Console URL on the web UI should be a Knox URL
> ----------------------------------------------------
>
> Key: KNOX-2675
> URL: https://issues.apache.org/jira/browse/KNOX-2675
> Project: Apache Knox
> Issue Type: Improvement
> Affects Versions: 1.4.0
> Reporter: Dénes Bodó
> Assignee: Dénes Bodó
> Priority: Major
> Fix For: 1.6.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When I open the Oozie web UI through Knox gateway and navigate to a
> workflow's action details then I see the Console URL field contains the
> cluster's internal hostname instead of a Knox gateway url. Here is an example
> json result from Oozie through Knox:
> {noformat}
> {
> "appName":"some_oozie_application",
> ...
> "actions":[
> {...},
> {
> ...
>
> "consoleUrl":"https://some_internal_domain_name:8090/proxy/application_1632125050865_0003/";,
> ...
> },
> {...}
> ],
> "status":"SUCCEEDED",
> "group":null
> } {noformat}
> The desired form should be for the consoleUrl field something like this:
> {noformat}
> https://externally_available_knox_domain_name:8443/gateway/cdp-proxy/yarn/cluster/app/application_1632125050865_0003/
> {noformat}
> The proposed solution contains Yarn UI v1 URL because the Yarn UI v2 contains
> a hash mark which cannot be used. See KNOX-2676
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
