Skip to content

doc: comment on spark history integration #559

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 22, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ All notable changes to this project will be documented in this file.
- Replace stackable-operator `print_startup_string` with `tracing::info!` with fields.
- BREAKING: Inject the vector aggregator address into the vector config using the env var `VECTOR_AGGREGATOR_ADDRESS` instead
of having the operator write it to the vector config ([#551]).
- Document that Spark Connect doesn't integrate with the history server ([#559])

### Fixed

Expand All @@ -28,6 +29,7 @@ All notable changes to this project will be documented in this file.
[#551]: https://github.com/stackabletech/spark-k8s-operator/pull/551
[#553]: https://github.com/stackabletech/spark-k8s-operator/pull/553
[#554]: https://github.com/stackabletech/spark-k8s-operator/pull/554
[#559]: https://github.com/stackabletech/spark-k8s-operator/pull/559

## [25.3.0] - 2025-03-21

Expand Down
6 changes: 5 additions & 1 deletion docs/modules/spark-k8s/pages/usage-guide/spark-connect.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -45,11 +45,15 @@ spec:

The example above adds a new endpoint for application metrics.

== Spark History Server

Unforunately integration with the Spark History Server is not supported yet.
The connect server seems to ignore the `spark.eventLog` properties while also prohibiting clients to set them programatically.

== Notable Omissions

The following features are not supported by the Stackable Spark operator yet

* Integration with the Spark History Server.
* Authorization and authentication. Currently, anyone with access to the Spark Connect service can run jobs.
* Volumes and volume mounts can be added only with pod overrides.
* Job dependencies must be provisioned as custom images or via `--packages` or `--jars` arguments.
Expand Down