*Hi team,*
We’re working on WI https://issues.apache.org/jira/browse/BEAM-3304 and have a couple of questions. As we understand it, the Proto compiler based on file beam_runner_api.proto creates the whole RunnerApi for Java (RunnerApi.class) and for Go (beam_runner_api.pb.go) TriggerTranslation.java uses several methods from the RunnerApi to translate from Trigger to Proto and viceversa which then get used for windowing strategies. Now, if we’re on the right path, what needs to be done as part of the *BEAM-3304* WI is - implement, for example, the AfterPane (called trigger ElementCount in Go) and - implement the TriggerTranslation code in Go along with the necessary plumbing, in order to expose that trigger to the user. - Implement WindowingStrategy in Go (sdks/go/pkg/beam/core/graph/window/strategy.go) Is this correct? Is there some important piece I’m missing? Thanks for the help! -- *This email and its contents (including any attachments) are being sent to you on the condition of confidentiality and may be protected by legal privilege. Access to this email by anyone other than the intended recipient is unauthorized. If you are not the intended recipient, please immediately notify the sender by replying to this message and delete the material immediately from your system. Any further use, dissemination, distribution or reproduction of this email is strictly prohibited. Further, no representation is made with respect to any content contained in this email.*
