hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsuyoshi OZAWA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11032) Replace use of Guava's Stopwatch with Hadoop's StopWatch
Date Thu, 08 Jan 2015 06:04:35 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-11032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268869#comment-14268869

Tsuyoshi OZAWA commented on HADOOP-11032:

Committing this to trunk and branch-2.

Thanks [~gsteelman] for reporting and reviews and thanks [~sjlee0], [~stevel@apache.org],
[~ajisakaa] for your reviews.

> 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: 3.0.0, 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

View raw message