[
https://issues.apache.org/jira/browse/HADOOP-16213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858775#comment-16858775
]
Sean Mackrory commented on HADOOP-16213:
----------------------------------------
Same as HADOOP-16211 - +1 on the code, but there's a different set of
hadoop-yarn failures we need to check are actually flaky.
> Update guava to 27.0-jre in hadoop-project branch-3.1
> -----------------------------------------------------
>
> Key: HADOOP-16213
> URL: https://issues.apache.org/jira/browse/HADOOP-16213
> Project: Hadoop Common
> Issue Type: Sub-task
> Affects Versions: 3.1.0, 3.1.1, 3.1.2
> Reporter: Gabor Bota
> Assignee: Gabor Bota
> Priority: Critical
> Attachments: HADOOP-16213-branch-3.1.001.patch,
> HADOOP-16213-branch-3.1.002.patch, HADOOP-16213-branch-3.1.003.patch,
> HADOOP-16213-branch-3.1.004.patch, HADOOP-16213-branch-3.1.005.patch,
> HADOOP-16213-branch-3.1.006.patch
>
>
> com.google.guava:guava should be upgraded to 27.0-jre due to new CVE's found
> CVE-2018-10237.
> This is a sub-task for branch-3.1 from HADOOP-15960 to track issues on that
> particular branch.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
