[ 
https://issues.apache.org/jira/browse/KNOX-2577?focusedWorklogId=585371&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-585371
 ]

ASF GitHub Bot logged work on KNOX-2577:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 19/Apr/21 21:00
            Start Date: 19/Apr/21 21:00
    Worklog Time Spent: 10m 
      Work Description: wypoon commented on pull request #435:
URL: https://github.com/apache/knox/pull/435#issuecomment-822781549


   @moresandeep I added a new service version, 0.4.3, as you suggested. The 
service definition is the same as the existing one (0.4.0), while the rewrite 
rules have the proposed changes.


-- 
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: 585371)
    Time Spent: 0.5h  (was: 20m)

> [Livy Service] Application and container log links should point to YARN UI v2
> -----------------------------------------------------------------------------
>
>                 Key: KNOX-2577
>                 URL: https://issues.apache.org/jira/browse/KNOX-2577
>             Project: Apache Knox
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Wing Yew Poon
>            Priority: Minor
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> In the Livy UI, when a session is created, a Spark application is started. In 
> the UI, there is a link to the YARN application and a link to the container 
> log for the Spark driver. Those links currently point to the old YARN UI; 
> they should point to the YARN UI v2.
> E.g.,
> /yarn/proxy/application_xxx -> /yarnuiv2/proxy/application_xxx
> and
> /yarn/nodemanager/node/containerlogs/container_xxx/... -> 
> /yarnuiv2/node/containerlogs/container_xxx/...



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

Reply via email to