dheerenmohta opened a new pull request, #71932:
URL: https://github.com/apache/airflow/pull/71932
Users triggering a Dag from the UI had no way to pass ad-hoc arguments to a
Spark application: SparkKubernetesOperator only accepted a full
application_file/template_spec, so any per-run value had to be baked into the
CRD spec ahead of time. Exposing application_arguments as a templated operator
param lets callers reference Dag run Params (e.g. arguments=["{{
params.input_path }}"]) and have them merged into the CRD's spec.arguments
field at submission time, following the same merge-into-template_body pattern
already used for driver/executor labels and the SPARK_APPLICATION_NAME env var.
The parameter is named application_arguments rather than arguments because
KubernetesPodOperator already defines an unrelated `arguments` param (driver
container entrypoint args); reusing that name would have silently changed its
meaning for this operator.
closes: #16728
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Code (Sonnet 5)
Generated-by: Claude Code (Sonnet 5) following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
