-
Notifications
You must be signed in to change notification settings - Fork 57
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
SNOW-1707031 hadoop upgrade for vulnerability fix #849
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing this!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, @sfc-gh-lsembera do we need to check with security about the added license?
I dont think so, it's existing license we are adding and it's a known one. |
Thanks, @sfc-gh-japatel. The only issue I see here is that it will further inflate the JAR size. Should we try to exclude the new dependencies and see whether tests pass? I don't see why would the SDK need Netty. |
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHADOOP-8089372
54d857e
to
8ab3e42
Compare
SNOW-1707031
Added few exclusions. Here is how I did it: I looked at the failed command of
mvn clean install
and compared it withmvn dependency:tree
Mostly it's about finding which dependencies can be excluded so that the new upgrade which brought in new dependencies are used.
Other minor fixes for merge gates to pass. Ran locally and it succeeeded