[BEAM-8348] set job_name in portable_runner.py job request#9789
[BEAM-8348] set job_name in portable_runner.py job request#9789ibzib wants to merge 2 commits intoapache:masterfrom
Conversation
There was a problem hiding this comment.
GoogleCloudOptions doesn't seem appropriate for this. Should we relocate the option?
There was a problem hiding this comment.
That was initially my preferred approach, but I don't see a way to do it without breaking all the existing Dataflow pipelines that set a job name. See #9724
There was a problem hiding this comment.
Would it be possible to replicate the option and deprecate it in GoogleCloudOptions?
FWIW this option also exists in the Flink runner and the job_name is already reflected in the pipeline (see #9752 (comment)), so what is the effect of this change going to be?
There was a problem hiding this comment.
PipelineOptions does not allow the same option to belong to multiple subclasses.
This PR changes job_name in the job request, not the pipeline options. e.g. here https://github.com/apache/beam/blob/master/runners/java-fn-execution/src/main/java/org/apache/beam/runners/fnexecution/jobsubmission/InMemoryJobService.java#L124
There was a problem hiding this comment.
I see, what is the user facing impact?
Regarding PipelineOptions, can it not be changed to allow for the co-existence of job_name in both classes for a transition period? @robertwb
There was a problem hiding this comment.
Yes, we could add an explicit @property in GoogleCloudOptions that delegates to the one in PipelineOptions.
There was a problem hiding this comment.
It's a good idea. Unfortunately, it looks like the override of __settatr__ would take precedence over the property's setter. I'm not too familiar with how all these Python internals work, though, so I could be missing something obvious?
There was a problem hiding this comment.
Huh. Perhaps override _visible_option_list?
|
Any update on this? |
|
I haven't made any progress on this. It's not a terribly important feature. |
|
This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@beam.apache.org list. Thank you for your contributions. |
Post-Commit Tests Status (on master branch)
Pre-Commit Tests Status (on master branch)
See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.