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

Split lzo serializers into a separate sbt project #261

Closed
istreeter opened this issue May 4, 2022 · 0 comments
Closed

Split lzo serializers into a separate sbt project #261

istreeter opened this issue May 4, 2022 · 0 comments

Comments

@istreeter
Copy link
Contributor

This is a breaking change, which means our standard s3-loader assets (the jar file and docker image) will not be able to output lzo compressed files.

Instead, users will need to pull the -distroless tagged docker images, e.g.

docker pull snowplow/snowplow-s3-loader:2.2.0-lzo

We are doing this because the lzo library depends on hadoop version 2, which is now very old and not so actively maintained. If high vulnerabilities are reported in hadoop version 2, then we have no easy way to mitigate them in s3 loader. But by confining lzo compression to a separate image, we can more easily maintain a "clean" image, free from security vulnerabilities, and OK to output gzipped files.

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

1 participant