Forum Discussion
Consuming compressed messages from Event Hub
Hello,
I need to create an Eventstream with Event Hub as a data source. Event Hub payload is compressed JSON, compressed with gzip and 'compression' property set on record level. There seems to be no option to specify that payload is gzip-compressed. Is there any way to make it work, except for decompressing elsewhere and having a duplicate Event Hub with decompressed payload?
A.
Hi Anonymous
At the moment, there's no official ETA for native gzip decompression support in Eventstream. However you can submit your idea in ideas forum. Fabric Ideas - Microsoft Fabric Community
If this solution helps, please consider giving us Kudos and accepting it as the solution so that it may assist other members in the community
Thank you.
5 Replies
Hi Anonymous
At the moment, there's no official ETA for native gzip decompression support in Eventstream. However you can submit your idea in ideas forum. Fabric Ideas - Microsoft Fabric Community
If this solution helps, please consider giving us Kudos and accepting it as the solution so that it may assist other members in the community
Thank you.Hi Anonymous
Could you please confirm if you've submitted this as an idea in the Ideas Forum? If so, sharing the link here would be helpful for other community members who may have similar feedback.
If we don’t hear back, we’ll go ahead and close this thread. For any further discussions or questions, please start a new thread in the Microsoft Fabric Community Forum we’ll be happy to assist.
Thank you for being part of the Microsoft Fabric Community.
Hi Anonymous
Thank you for reaching out microsoft fabric community forum.You're right—Eventstream doesn't currently support handling gzip-compressed payloads from Event Hub directly, even if there's a compression property in each record.
The recommended approach is to use an intermediate service (like Azure Functions, Stream Analytics, or Data Factory) to read from the Event Hub, decompress the data, and forward it to another Event Hub or a supported input for Eventstream.
While maintaining a second Event Hub with decompressed data isn’t ideal, it’s the most practical solution for now.
If this solution helps, please consider giving us Kudos and accepting it as the solution so that it may assist other members in the community
Thank you.