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 "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/03/02 18:04:06 UTC

[jira] [Updated] (HADOOP-11032) Replace use of Guava's Stopwatch with Hadoop's StopWatch

     [ https://issues.apache.org/jira/browse/HADOOP-11032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer updated HADOOP-11032:
--------------------------------------
    Fix Version/s:     (was: 3.0.0)

> Replace use of Guava's Stopwatch with Hadoop's StopWatch
> --------------------------------------------------------
>
>                 Key: HADOOP-11032
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11032
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Gary Steelman
>            Assignee: Tsuyoshi Ozawa
>             Fix For: 2.7.0
>
>         Attachments: HADOOP-11032.1.patch, HADOOP-11032.2.patch, HADOOP-11032.3.patch, HADOOP-11032.3.patch, HADOOP-11032.3.patch, HADOOP-11032.3.patch, HADOOP-11032.3.patch, HADOOP-11032.4.patch, HADOOP-11032.5.patch, HADOOP-11032.6.patch, HADOOP-11032.7.patch, HADOOP-11032.8.patch, HADOOP-11032.8.patch
>
>
> This patch reduces Hadoop's dependency on an old version of guava. Stopwatch.elapsedMillis() isn't part of guava past v16 and the tools I'm working on use v17. 
> To remedy this and also reduce Hadoop's reliance on old versions of guava, we can implement original StopWatch based on Guava's one and Apache's one.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)