-
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
File source should expand support for other file compression algorithms (zip, bzip, lzma, zstd etc.) #13500
Comments
While this feature request is indeed very useful, please don't forget to take a look at this issue #13193 first :) |
Thanks for creating the issue ticket. Some of the windows servers with only native .zip compression is allowed (by organization) for log files will benefit from this (including me of course!) |
Just a veeeeeeeeeeery small note about Zip. Zip is not a compression method - that is just a file format that internally supports different compression methods. As a For other algorithms I guess this library could be kinda interesting - https://github.com/Nemo157/async-compression/ (or integrate other algorithms directly with the corresponding libraries). From my perspective, support for other compression algorithms is really important. Especially, I am interested in |
Related issue: #2302 |
@jszwedko Could you please clarify, in which exactly compression algorithms Vector is interested? I guess I can help here with the integration somehow (since I have some free time). Probably some of them are more important than others. Also, since the compression story seems to be quite big (a lot of compression algorithms, different sinks support different compression algorithms subset, Vector does not support yet setting compression level, etc) maybe would be a good decision to create an epic for the compression story and track there the progress. |
Thanks for the note @zamazan4ik ! I'm actually curious to hear from others using the As you note, compression support is spotty and source / sink specific. It does seem like we could take a more generalized approach here, similar to how codecs are implemented, to generalize the compression. It'd require some deep architectural work though, which is probably best started with an RFC document. In absence of that, we are happy to see additional algorithms added to specific sources and sinks. It sounds like |
Closing in-lieu of #16891 |
A note for the community
Use Cases
While less common than gzip, these compression algorithms are in the field and support for them would expand the scope of users leveraging the
file
source.Attempted Solutions
No response
Proposal
No response
References
No response
Version
0.23
The text was updated successfully, but these errors were encountered: