You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Sunil Govindan (JIRA)" <ji...@apache.org> on 2018/08/29 04:19:00 UTC
[jira] [Commented] (HADOOP-14238) [Umbrella] Rechecking Guava's
object is not exposed to user-facing API
[ https://issues.apache.org/jira/browse/HADOOP-14238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595917#comment-16595917 ]
Sunil Govindan commented on HADOOP-14238:
-----------------------------------------
[~xiaochen] [~ozawa]
As this jira is marked for 3.2 as a blocker, cud u pls help to take this forward or move out if its not feasible to finish in coming weeks. 3.2 code freeze date is nearby in a weeks. Kindly help to check the same.
> [Umbrella] Rechecking Guava's object is not exposed to user-facing API
> ----------------------------------------------------------------------
>
> Key: HADOOP-14238
> URL: https://issues.apache.org/jira/browse/HADOOP-14238
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Tsuyoshi Ozawa
> Priority: Critical
>
> This is reported by [~hitesh] on HADOOP-10101.
> At least, AMRMClient#waitFor takes Guava's Supplier instance as an instance.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org