@dreamoka checked internally, and apparently the file splitting connector will not be open-source. It’s getting close to release though, so keep an eye out here for at least a way to trial/demo it. It’s part of our broader “File Mesh” strategy for helping make MFT more event-driven.
@forward100 , welcome to the Community! I’m impressed you got such good compression, must be very repetitive JSON or XML or something? I’m wondering though: were you comparing the API payload compression feature with the streaming connection compression, or were you trying to use both together and not seeing any additional improvement? If the latter, it makes sense that you wouldn’t see much improvement as the payload is already compressed, and only the message header (which is mostly binary) would be available to be compressed, which probably wouldn’t do much of anything.