:memo: Publish kyuubi-spark-authz Spark 4.0 binary to Maven Central
- Dominant language
- Scala
- Stars
- 2.4k
- Forks
- 1k
- PR merge metrics
- No merged PRs in 30d
Description
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
### Search before asking
- [x] I have searched in the [issues](https://github.com/apache/kyuubi/issues?q=is%3Aissue) and found no similar issues.
### What type of changes will we make to the documentation?
Showcase
### Affects Version(s)
master,1.11.1
### Improving the documentation
TL;DR — Spark 4 compile support landed in #7256 (v1.10.3 / v1.11.x), but no Spark-4 artifact is published to Maven Central ([https://mvnrepository.com/artifact/org.apache.kyuubi/kyuubi-spark-authz](https://mvnrepository.com/artifact/org.apache.kyuubi/kyuubi-spark-authz)). Requesting it be added to the release matrix.
Use case
We run Spark 4.0 with Ranger-based authz. v1.11.1 builds cleanly from source against Spark 4.0 / Scala 2.13 / Java 21 using -Pspark-4.0, so we're currently building and hosting the jar on an internal repo. A published artifact on Central would let us — and other Spark 4 users — consume it directly.
Ask
Add a Spark 4 variant of kyuubi-spark-authz to the release matrix so future releases publish it to Maven Central. Happy to open a PR if a committer can point me at how the existing Spark 3.5 release is wired.
Related: #7256
### Are you willing to submit PR?
- [x] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
- [ ] No. I cannot submit a PR at this time.
Contributor guide
Research direction
Start by comparing the existing Spark 3.5 release wiring with the Spark 4.0 profile mentioned in #7256 and -Pspark-4.0; locate the release matrix entry that controls kyuubi-spark-authz publication. Done means the Spark 4 variant is included in a release build and published to Maven Central.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, scala
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100