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

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

                Author: ASF GitHub Bot
            Created on: 18/Sep/26 07:00
            Start Date: 18/Sep/26 07:00
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on PR #1413:
URL: https://github.com/apache/knox/pull/1413#issuecomment-5726405908

   ## Test Results
     4 files    4 suites   25s ⏱️
    98 tests  98 ✅ 0 💤 0 ❌
   116 runs  116 ✅ 0 💤 0 ❌
   
   Results for commit ff441687.
   
   
[test-results]:data:application/gzip;base64,H4sIAHPhrGoC/13MyQ6CMBSF4VchXbug0On6MqZj0gjUdFgR391CAKvL7z/JWZHzk03o3pFbh1Lx+YIpUWYflsqBVtclbxuIE49UtP4rT/+qpb+Ck376CTbGEI8Sy7I9YswOnI9t+T7ubg53t386zLPPFcg5QjAT3IAaRgnAAKzhanSul2CF5FpRpqhG7w+wvkYZAgEAAA==
   




Issue Time Tracking
-------------------

    Worklog Id:     (was: 1042550)
    Time Spent: 0.5h  (was: 20m)

> Add Knox service definition for Spark 4 History Server UI (spark4historyui)
> ---------------------------------------------------------------------------
>
>                 Key: KNOX-3474
>                 URL: https://issues.apache.org/jira/browse/KNOX-3474
>             Project: Apache Knox
>          Issue Type: Task
>            Reporter: Arun Kumar M
>            Priority: Major
>         Attachments: image-2026-09-18-01-10-32-387.png, 
> image-2026-09-18-01-10-40-022.png
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> *Summary*
> Add upstream Knox support for the Spark 4 History Server Web UI (role: 
> SPARK4HISTORYUI).
>  
> *Motivation*
> Knox already supports spark3historyui (SPARK3HISTORYUI). Spark 4 deployments 
> need an equivalent service definition so the History Server UI is reachable 
> through Knox and linked correctly from YARN ResourceManager UI.
>  
> *Implementation*
> Base on existing spark3historyui/3.0.0/ pattern:
>  
> | Item | Value |
> |------|-------|
> | Service role | SPARK4HISTORYUI |
> | Service name / URL path | spark4history |
> | Metadata type | UI |
> | shortDesc | Spark 4 History Server Web UI |
> | CM discovery | Spark4HistoryUIServiceModelGenerator (extend 
> SparkHistoryUIServiceModelGenerator) |
> | CM service type | SPARK4_ON_YARN (align with CM Spark 4 service type) |
> | CM role type | SPARK4_YARN_HISTORY_SERVER (align with CM Spark 4 role type) 
> |
>  
> *Scope*
> *1. Service definition*
> - gateway-service-definitions/services/spark4historyui/3.0.0/service.xml
> - gateway-service-definitions/services/spark4historyui/3.0.0/rewrite.xml
> - Inbound/outbound rewrite rules for /spark4history/, /history/, jobs pages, 
> SSO header filters
>  
> *2. Cloudera Manager discovery*
> - Spark4HistoryUIServiceModelGenerator.java + unit tests
> - META-INF/services ServiceModelGenerator registration
> - ClouderaManagerServiceDiscoveryTest (HTTP and SSL port variants)
>  
> *3. YARN UI cross-links (required for RM → Spark 4 History navigation)*
> - gateway-service-definitions/services/yarnui/2.7.0/rewrite.xml
> - Add spark4history redirect rule parallel to existing spark3history rule
> - Pattern: *://*:*/history/\{**}?spark4=true?\{**} → 
> \{$frontend[url]}/spark4history/history/\{**}?\{**}
> - gateway-service-definitions/services/yarnuiv2/3.0.0/rewrite.xml
> - Same spark4history rule as above
>  
> *4. Admin / configuration*
> - gateway-admin-ui: add SPARK4HISTORYUI to service role list
> - Homepage icon for Spark 4 History Server (if icon metadata support is 
> included)
>  
> *Out of scope*
> - Spark History Server SPNEGO / authentication configuration
> - Spark 4 parcel installation issues
>  
> *Acceptance criteria*
> - /spark4history/** routes to Spark 4 History Server backend through Knox
> - CM discovery resolves SPARK4HISTORYUI URLs (HTTP and HTTPS)
> - YARN RM UI links with ?spark4=true route to Knox spark4history path
> - Service tile appears on Knox Homepage
> - Unit tests pass



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to