onlyarnav opened a new issue, #71053:
URL: https://github.com/apache/airflow/issues/71053
### Under which category would you file this issue?
Providers
### Apache Airflow version
3.3.0
### What happened and how to reproduce it?
### Description
In `_YarnSparkSubmitBackend.submit_job`
(`airflow/providers/apache/spark/operators/spark_submit.py`), implicit string
literal concatenation across lines lacks a space between adjacent string tokens:
```python
raise ValueError(
"spark.yarn.submit.waitAppCompletion=true cannot be set for cluster mode
as it conflicts"
"with the need to exit spark-submit immediately to persist the
application ID for tracking. "
"Either remove the explicit conf or set durable=False."
)
```
This currently renders to the user as: `...cannot be set for cluster mode as
it conflictswith the need to exit...`
### Context
Follow-up to PR #68679 (refactoring SparkSubmitOperator backends into
strategy classes).
### Proposed Change
Add a trailing space after `"conflicts "` so that the raised ValueError
formats correctly as `"conflicts with the need"`, and update the unit test in
`test_spark_submit.py` to assert the formatted error string.
### What you think should happen instead?
_No response_
### Operating System
_No response_
### Deployment
None
### Apache Airflow Provider(s)
_No response_
### Versions of Apache Airflow Providers
_No response_
### Official Helm Chart version
Not Applicable
### Kubernetes Version
_No response_
### Helm Chart configuration
_No response_
### Docker Image customizations
_No response_
### Anything else?
_No response_
### Are you willing to submit PR?
- [x] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
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]
