Skip to content
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

Compress messages before publishing - Google Pub/Sub #280

Open
kk2491 opened this issue Jun 15, 2021 · 4 comments
Open

Compress messages before publishing - Google Pub/Sub #280

kk2491 opened this issue Jun 15, 2021 · 4 comments

Comments

@kk2491
Copy link

kk2491 commented Jun 15, 2021

Hi All,

I am new to Google pub/sub.

Considering the maximum limit for the publish message is 10 MB, is there a way to compress the messages before publishing the data to a topic.

While going through I found this article, however I am not really sure if this is recommended by GCP as I was not able to get the resources in GCP.

Your help would be really appreciated.

Thank you

@kir-titievsky
Copy link
Contributor

Pub/Sub PM here. Just a note that this is makes sense as a feature request. I've heard this from another customer who quoted a 5-10X compression ratios for JSON data. Since Kafka can compress data "on the wire", this can mean that without Pub/Sub-side compression the output bandwidth of the sink connector is 5-10X the input.

We'll have to think about how to support this properly.

@kk2491
Copy link
Author

kk2491 commented Jul 20, 2021

@kir-titievsky Thanks for the response. It would be very helpful if some kind compression is in place in pubsub msgs.

Thank you

@kir-titievsky
Copy link
Contributor

@kk2491 understood. We'll keep this bug open as a feature request. I agree this would be a good for us to add, although, cannot at the moment say when we can get to this. In the meantime, consider the recommendation to compress each message body in the application code as official.

@kk2491
Copy link
Author

kk2491 commented Jul 31, 2021

@kir-titievsky Thank you. 👍🏾

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants