[
https://issues.apache.org/jira/browse/KNOX-3473?focusedWorklogId=1042446&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1042446
]
ASF GitHub Bot logged work on KNOX-3473:
----------------------------------------
Author: ASF GitHub Bot
Created on: 17/Sep/26 19:03
Start Date: 17/Sep/26 19:03
Worklog Time Spent: 10m
Work Description: samuhasavak5 opened a new pull request, #1412:
URL: https://github.com/apache/knox/pull/1412
KNOX-3473 - Add livy_for_spark4 Knox service definition
Depends on #1411
## What changes were proposed in this pull request?
This PR adds upstream Knox support for the dedicated Livy for Spark 4
service (role: LIVY_FOR_SPARK4).
Problem: Knox has no service definition for Livy for Spark 4. Deployments
running a separate Livy for Spark 4 instance cannot be proxied or discovered
through Knox, and the Knox Homepage cannot show a dedicated Livy for Spark 4
tile with the correct logo.
Solution: Introduce livy_for_spark4 by mirroring the livy_for_spark3 service
definition (KNOX-3472 / #1411) with Spark 4 naming, CM discovery, admin UI
registration, homepage logo, and unit tests. Routing reuses
org.apache.knox.gateway.livy.LivyDispatch.
### Changes
File | Change
Issue Time Tracking
-------------------
Worklog Id: (was: 1042446)
Remaining Estimate: 0h
Time Spent: 10m
> Add Knox service definition for Livy for Spark 4 (livy_for_spark4)
> ------------------------------------------------------------------
>
> Key: KNOX-3473
> URL: https://issues.apache.org/jira/browse/KNOX-3473
> Project: Apache Knox
> Issue Type: Task
> Reporter: Arun Kumar M
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *Summary*
> Add upstream Knox support for Livy for Spark 4 (role: LIVY_FOR_SPARK4).
>
> *Depends on*
> KNOX-3472 (livy_for_spark3) — mirror the same structure with Spark 4 naming.
>
> *Implementation*
> Mirror livy_for_spark3 with these identifiers:
>
> | Item | Value |
> |------|-------|
> | Service role | LIVY_FOR_SPARK4 |
> | Service name / URL path | livy_for_spark4 |
> | CM service type | LIVY_FOR_SPARK4 |
> | CM role type | LIVY_SERVER_FOR_SPARK4 |
> | Discovery class | LivyForSpark4ServiceModelGenerator |
> | Dispatch | org.apache.knox.gateway.livy.LivyDispatch |
> | Icon | livyserver.png (same as Spark 3) |
>
> *Scope (parallel file set to KNOX-3472)*
> - gateway-service-definitions/services/livy_for_spark4/0.6.0/service.xml +
> rewrite.xml
> - gateway-discovery-cm/.../LivyForSpark4ServiceModelGenerator.java + unit
> tests
> - META-INF/services ServiceModelGenerator registration
> - ClouderaManagerServiceDiscoveryTest for LIVY_FOR_SPARK4
> - gateway-admin-ui: add LIVY_FOR_SPARK4 to service role list
> - gateway-release/home/conf/gateway-site.xml: add LIVY_FOR_SPARK4 to
> x-forwarded servicename list
>
> *Out of scope*
> - Per-instance HA routing (same as KNOX-3472)
>
> *Acceptance criteria*
> - livy_for_spark4 routes correctly through Knox proxy
> - CM discovery resolves LIVY_FOR_SPARK4 backend URLs
> - Service visible on Knox Homepage and Admin UI descriptor wizard
> - All new unit tests pass
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
