Github user liyinan926 commented on the issue:
https://github.com/apache/spark/pull/21067
+1 on what @foxish said. If using a Job is the right way to go ultimately,
it's good to open discussion with sig-apps on adding an option to the Job API &
controller to use deterministic pod names as well as to offer the exactly-once
semantic. Spark probably is not the only use case needing such a semantic
guarantee.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
