Skip to content
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

[WIP] [BEAM-9120] Deprecate onSuccessMatcher, onCreateMatcher #10589

Closed
wants to merge 1 commit into from

Conversation

TheNeuralBit
Copy link
Member

WIP: Do not merge until the various places we use these flags have been removed!

Post-Commit Tests Status (on master branch)

Lang SDK Apex Dataflow Flink Gearpump Samza Spark
Go Build Status --- --- Build Status --- --- Build Status
Java Build Status Build Status Build Status Build Status
Build Status
Build Status
Build Status Build Status Build Status
Build Status
Build Status
Python Build Status
Build Status
Build Status
Build Status
--- Build Status
Build Status
Build Status
Build Status
--- --- Build Status
XLang --- --- --- Build Status --- --- ---

Pre-Commit Tests Status (on master branch)

--- Java Python Go Website
Non-portable Build Status Build Status
Build Status
Build Status Build Status
Portable --- Build Status --- ---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

@markflyhigh
Copy link
Contributor

Sorry for late review. I'll take a look at it today

@@ -102,8 +101,6 @@ DataflowPipelineJob run(Pipeline pipeline, DataflowRunner runner) {
job.getJobId(),
expectedNumberOfAssertions);

assertThat(job, testPipelineOptions.getOnCreateMatcher());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes sure test fail-fast if pipeline creation failed. Do we have alternative solutions?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it do that? My understanding was that this would be a no-op by default, since OnCreateMatcher is an instance of AlwaysPassMatcher. It will only fail fast if the user sets an OnCreateMatcher, which I don't think is happening anywhere outside of TestDataflowRunnerTest.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it wasn't used in any of the integration tests. I think it's okay to remove since the following waitForxxxJobTermination is monitoring the job status.

@TheNeuralBit
Copy link
Member Author

Run Java PreCommit

@stale
Copy link

stale bot commented Mar 22, 2020

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.

@stale stale bot added the stale label Mar 22, 2020
@stale
Copy link

stale bot commented Mar 29, 2020

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.

@stale stale bot closed this Mar 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants