[BEAM-7819] Add missing fields to python apache_beam.io.gcp.pubsub.PubsubMessage#14767
[BEAM-7819] Add missing fields to python apache_beam.io.gcp.pubsub.PubsubMessage#14767pabloem merged 1 commit intoapache:masterfrom odenio:add-missing-pubsubmessage-attrs
Conversation
|
R: @pabloem Is it expected that the formatter/lint tests will fail? It's mostly indentation errors on lines I haven't changed |
It seems to be failing on the lines you have changed. Please try fixing those. |
|
@aaltay ugh, my editor was configured to auto-apply Black formatting on save of any .py file and much ugliness ensued as a result. I've pried it all out and the format/lint tests are passing now. ...but obviously the precommit test is not. But the precommit test suite is so enormous that I'm having trouble seeing in the logs what portion of that might be related to my change. FWIW, (Edit: spot-checked some of the failures, and it looks like |
If it is broken on master you do not need to worry about it now. Let's get it reviewed and hopefully master would be fixed by that time. |
I don't see that FlinkRunnerTestStreaming failed in https://ci-beam.apache.org/job/beam_PreCommit_Python_Commit/18572/ (IIRC Flink tests are skipped in this job, so I wonder if you are testing a different command than the precommit uses?). Instead I see |
|
Run Python PreCommit |
1 similar comment
|
Run Python PreCommit |
|
Python precommit has finally passed, looks like the failures were indeed flakes. I filed BEAM-12322 to track this issue. |
…bsubMessage - Add the `publish_time`, `message_id` and `ordering_key` attributes to the PubsubMessage class - Convert google.protobuf.timestamp_pb2.Timestamp to python datetime in _from_proto_str - Ensure `message_id` and `publish_time` fields are unset in WriteToPubsub
|
Run Python PreCommit |
1 similar comment
|
Run Python PreCommit |
|
Run Python 3.8 PostCommit |
|
LGTM. Thanks! |
|
@pabloem I was a little surprised to find that this didn't make it into the 2.30.0 release. Should I expect it in 2.31? |
|
Here is a link to the release policy: https://beam.apache.org/contribute/release-guide/ Once the release branch is cut, you can check to see if your change is included. This change will be included in the 2.31.0 release. |
|
Release branches are publicly visible at |
|
It’s been months now and this still hasn’t been included in a release. As @n-oden said back in June, “is there a timeline for this actually landing on a release branch?” |
|
@astorrs All changes are automatically picked up by a "release cut" that happens roughly once every 6 weeks. https://beam.apache.org/contribute/#when-will-my-change-show-up-in-an-apache-beam-release This change was included starting with the 2.31.0 release of Beam in June. If you still see this bug in newer versions of Beam, please let us know. |
publish_time,message_idandordering_keyattributes to the PubsubMessage class
datetime in _from_proto_str
message_idandpublish_timefields are unsetin WriteToPubsub
This also addresses [BEAM-10958]
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.
ValidatesRunnercompliance status (on master branch)Examples testing status on various runners
Post-Commit SDK/Transform Integration 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.
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.