-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[BEAM-12751] Set clientRequestId for Dataflow python job creation #15335
Conversation
@pabloem , could you take a look at this PR? |
I'll look. Thanks @baeminbo |
Run Python PreCommit |
Run Python 3.8 PostCommit |
Codecov Report
@@ Coverage Diff @@
## master #15335 +/- ##
==========================================
- Coverage 83.81% 83.68% -0.14%
==========================================
Files 441 440 -1
Lines 59773 59958 +185
==========================================
+ Hits 50101 50174 +73
- Misses 9672 9784 +112
Continue to review full report at Codecov.
|
Run Python 3.8 PostCommit |
Please hold on reviewing this PR. It looks like job creation doesn't work as intended in the following scenario.
I saw (1) and (2) have different |
okay - can you please ping me whenever you've debugged that? thanks! |
1e23d3d
to
c86bfa1
Compare
@pabloem I fixed the issue of not-failing for already-existing job above. For this, I added a logic to check the |
LGTM thanks |
Current Dataflow pipeline python runner doesn't specify clientRequestId which causes job creation API retry to fail with "There is already an active job named...". Java runner doesn't have this issue as it sets clientRequestId properly.
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username
).[BEAM-XXX] Fixes bug in ApproximateQuantiles
, where you replaceBEAM-XXX
with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.CHANGES.md
with noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
ValidatesRunner
compliance status (on master branch)Examples testing status on various runners
Post-Commit SDK/Transform Integration 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.
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.