-
Notifications
You must be signed in to change notification settings - Fork 4.5k
[#21761] Add GCP Project as pipeline opt read by expansion service #21852
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
Conversation
|
Run XVR_GoUsingJava_Dataflow PostCommit |
|
R: @chamikaramj |
|
Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control |
|
This seems like the best approach would be to have this extra pipeline option only read while using the GCP expansion service, but I'm not sure if there's a straightforward way to alter the behavior only when using that expansion service |
.../expansion-service/src/main/java/org/apache/beam/sdk/expansion/service/ExpansionService.java
Outdated
Show resolved
Hide resolved
|
I've changed it so that now GcpExpansionService is a derived class of the original ExpansionService, and only that class receives the project pipeline option. So only the GCP expansion service jar has grown. |
|
Run Go PostCommit |
|
Run XVR_GoUsingJava_Dataflow PostCommit |
|
Looks like the test is still failing, which means my local environment isn't replicating the bug. I'll look into this tomorrow. |
|
Run XVR_GoUsingJava_Dataflow PostCommit |
1 similar comment
|
Run XVR_GoUsingJava_Dataflow PostCommit |
The expansion service now reads the Project pipeline option so that during expansion it can perform GCP operations on the correct project. Also un-sickbay a test that was blocked on this issue.
This makes some changes to ExpansionService.java to allow performing additional configuration in subclasses.
|
Run XVR_GoUsingJava_Dataflow PostCommit |
2 similar comments
|
Run XVR_GoUsingJava_Dataflow PostCommit |
|
Run XVR_GoUsingJava_Dataflow PostCommit |
|
Looks like it still fails to get the projectID, but it could be just in how the Go SDK is providing it in pipeline options (or not).
|
|
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. |
|
This pull request has been closed due to lack of activity. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time. |
The expansion service now reads the Project pipeline option so that during expansion it can perform GCP operations on the correct project. Also un-sickbay a test that was blocked on this issue.
Bug: #21761
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username).addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>instead.CHANGES.mdwith noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.