[
https://issues.apache.org/jira/browse/HADOOP-16055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747901#comment-16747901
]
Steve Loughran commented on HADOOP-16055:
-----------------------------------------
Didn't notice that branch-2 was on the 199 version, that generates lots of NPE
warnings in the logs unless AWS metrics are wired up.
How about
# we look @ '271 to make sure its shaded Jackson is considered safe.
# otherwise, upgrade them all across 2.9 + with whatever fixes for regressions
are needed.
# And for 2.8, cherry pick in the shaded code from 2.9 as well
At least that way we are consistent, and with the shading its going to be less
transitively traumatic. The only impact is the shaded jar is *big*, which
doesn't just hurt the distro, it can slow down jetty scanning it for servlets.
Only a second or two, but did create problems with Ambari. Too bad.
bq. 2.7.x line is much harder, maybe we can stop the maintenance work rather
than upgrading AWS SDK versions.
something to discuss. If it's kept alive, maybe exclude the aws SDK From the
.tarball, though that leaves the problem about POMs open.
> Upgrade AWS SDK to fix license issue in branch-2.8 and branch-2.7
> -----------------------------------------------------------------
>
> Key: HADOOP-16055
> URL: https://issues.apache.org/jira/browse/HADOOP-16055
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Reporter: Akira Ajisaka
> Assignee: Akira Ajisaka
> Priority: Blocker
> Attachments: HADOOP-16055-branch-2.8-01.patch,
> HADOOP-16055-branch-2.8-02.patch
>
>
> Per HADOOP-13794, we must exclude the JSON license.
> The upgrade will contain incompatible changes, however, the license issue is
> much more important.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
