[blog] - Beam YAML protobuf blogpost
A blog post explaining Beam YAML's streaming capabilities, showcasing how to handle Protobuf events.
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
- [ ] Mention the appropriate issue in your description (for example:
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. - [ ] Update
CHANGES.mdwith noteworthy changes. - [ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.
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 or the workflows README to see a list of phrases to trigger workflows.
@brucearctor If you want to take a look and drop some comments if you see potential improvements
I'll take a look.
Responding quickly, and without taking much of a look yet [ nor being familiar with Beam's blog infra ] --> is there an 'easy' way to view how it renders? Besides reading the Markdown and text, it'd be good to visualize that it's fine. I'm just waking up, so it probably is standard markdown and my mind not fully awake yet.
Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:
R: @rszper for label website.
Available commands:
stop reviewer notifications- opt out of the automated review toolingremind me after tests pass- tag the comment author after tests passwaiting on author- shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)
The PR bot will only process comments in the main thread (not review comments).
R: @liferoad for final approval
cc @Polber
@ffernandez92 and others -- to not let this PR rot, is there anything else need to be addressed?
LGTM. Thanks a lot!