-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[BEAM-95] Use snappy compression on objects serialized via SerializabUtils #22
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
R: @dhalperi |
R: @kennknowles |
LGTM |
davorbonaci
added a commit
to GoogleCloudPlatform/DataflowJavaSDK
that referenced
this pull request
Mar 8, 2016
echauchot
added a commit
to echauchot/beam
that referenced
this pull request
May 12, 2017
Workaround for issue apache#22 + extra cleaning
echauchot
added a commit
to echauchot/beam
that referenced
this pull request
May 12, 2017
mareksimunek
pushed a commit
to mareksimunek/beam
that referenced
this pull request
May 9, 2018
#! Mention maven dependencies in README.md
robertwb
pushed a commit
to robertwb/incubator-beam
that referenced
this pull request
Apr 30, 2020
* Migrate github_sample functionality from Jekyll to Hugo * fixup! Migrate github_sample functionality from Jekyll to Hugo
hengfengli
referenced
this pull request
in hengfengli/beam
Mar 21, 2022
When we are splitting a wait for child partitions or a wait for parent partitions we need to make sure the restriction residual does not skip a phase, when scheduled before the primary. This is problematic in the case where the primary resumes, such as in the wait for child partitions / wait for parent partitions. In this PR, when splitting one of the two aforementioned modes, we remain at the same mode, instead of advancing. This will make sure the residual only proceeds if the current phase is complete.
sjvanrossum
pushed a commit
to sjvanrossum/beam
that referenced
this pull request
May 17, 2023
…methods-from-PValue refactor: remove PValue::register_pipeline_*() methods …
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
R: @davorbonaci