Add Spark application id to SparkApplication

Open
  • Is something wrong?
#805 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
kubernetes, rust
Domain
backend, distributed-systems

Research direction

Read the SparkApplication status types and the code that updates status from Spark application state. Find where the Spark application id becomes available, then trace how status fields are exposed. Done means the id is recorded in SparkApplication status so it can be used to link to the history server; the issue does not name specific files or tests.

Written by the indexing model from the issue text.

Description

Adding the application id to the SparkApplication status would e.g. allow us to link a SparkApplication to its entry in the history server. This has overlap with https://github.com/stackabletech/spark-k8s-operator/issues/538 but covers a different use case.

Dominant language
Rust
Stars
74
Forks
6
Avg merge
1d 1h
Merged PRs (30d)
15

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/spark-k8s-operator

All issues in stackabletech/spark-k8s-operator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.