[ 
https://issues.apache.org/jira/browse/KNOX-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arun Kumar M updated KNOX-3473:
-------------------------------
    Description: 
*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

  was:
Add upstream Knox support for Livy for Spark 4 (role: LIVY_FOR_SPARK4).

Implementation:
Mirror livy_for_spark3 service definition with Spark 4 naming:
 - Service role: LIVY_FOR_SPARK4
 - Service name/path: livy_for_spark4
 - CM role: LIVY_SERVER_FOR_SPARK4
 - CM discovery: LivyForSpark4ServiceModelGenerator
 - Icon: livyserver.png (same as Spark 3)

Depends on: KNOX-XXXX (livy_for_spark3) — or can be same PR series

Source: CDH/knox PR #796 (split out livy_for_spark4 commits)


> 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
>
> *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)

Reply via email to