-
Notifications
You must be signed in to change notification settings - Fork 4.5k
[BEAM-9562] Remove TimerSpec from Proto #11216
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
lukecwik
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remember that you can run the Python portable validates runner tests using Flink (./gradlew :runners:flink:1.9:job-server:validatesPortableRunner). This should give you good coverage as to whether the change as a whole works.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest not changing the proto tag numbers otherwise you'll have a more difficult import/update issue with Google.
It will be much easier as a separate change to renumber them in increasing order, so timer_family_specs is 5, restriction_coder_id is 6, requests_finalization is 7, ... (making the import into Google much simpler to do).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shouldn't this method replace to_runner_api?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm working on the Java changes meanwhile having some python tests to run to catch any breakages. Changing to to_runner_api is the next step. We should also remove TimerSpec definition from proto as long as nowhere else uses it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 on TimerSpec removal
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can rename this method to to_runner_api and remove the method below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| # TODO(BEAM-9602): Provide support of dynamic timer | |
| # TODO(BEAM-9602): Provide support for dynamic timer |
|
Retest all please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can rename this method to to_runner_api and remove the method below.
|
Run Java Flink PortableValidatesRunner Streaming |
|
Run Java Flink PortableValidatesRunner Streaming |
|
Run Java PreCommit |
|
Run JavaPortabilityApi PreCommit |
|
Run Java Flink PortableValidatesRunner Streaming |
|
Run Portable_Python PreCommit |
|
Run Python2_PVR_Flink PreCommit |
|
Run Python PreCommit |
|
Run Java_Examples_Dataflow PreCommit |
|
Run Portable_Python PreCommit |
|
Run Java Flink PortableValidatesRunner Streaming |
|
All tests passed. Going to merge it. Thanks for your help! |
|
@boyuanzz @lukecwik Run Dataflow ValidatesRunner (beam_PostCommit_Java_ValidatesRunner_Dataflow) started failing after this PR: History: I appreciate if you can check whether the failure is related to this PR. Created an issue: https://issues.apache.org/jira/browse/BEAM-9636 |
Thanks for the notification. Looking. |

This PR removes TimerSpec from Proto. Timer will be translated into TimerFamilySpec over fnapi.
R: @lukecwik
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-XXXwith the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.CHANGES.mdwith noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
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.