stackabletech / stackabletech/spark-k8s-operator
Spark options set by the user are not handled properly
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 4
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 15
Description
Affected Stackable version
all
Affected Apache Spark-on-Kubernetes version
all
Current and expected behavior
Spark properties that are set by both the user via spec.sparkConf and the operator are not merged properly.
Example: users that need to set Java proxy settings via spark.driver.extraJavaOptions cannot do so without overriding the same property set by the operator.
Possible solution
No response
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
None
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the handling of spec.sparkConf and the operator-generated Spark properties, then reproduce the conflict described for spark.driver.extraJavaOptions. Done means user-provided and operator-set properties are merged so required user settings are preserved without overriding the operator's settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust, spark
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100