-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
fix(gcp_pubsub source): Remove Tonic default 4MB decode size limit #22091
Conversation
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.
Thanks for this fix @sbalmos ! Agreed that we should match the old tonic
behavior as we did for the vector
sink. In the future, we could make this user-configurable.
This seems to be blocked from merging because the unrelated |
Those should be fixed on |
…ectordotdev#22091) * Remove Tonic default 4MB decode size limit * Changelog entry * Update changelog.d/22090_remove_gcp_pubsub_msg_size_limit.fix.md --------- Co-authored-by: Jesse Szwedko <[email protected]> Co-authored-by: Jesse Szwedko <[email protected]>
Summary
Removes the default 4MB message size decoding limit created by Tonic 0.9, preventing the gcp_pubsub source from receiving messages larger than this size.
Change Type
Is this a breaking change?
How did you test this PR?
Created a test PubSub topic in a personal GCP account, published a >4MB size message to the topic, and read from the subscription successfully.
Does this PR include user facing changes?
Checklist
Cargo.lock
), pleaserun
dd-rust-license-tool write
to regenerate the license inventory and commit the changes (if any). More details here.References