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 "Zoran Dimitrijevic (JIRA)" <ji...@apache.org> on 2015/04/24 19:28:39 UTC

[jira] [Updated] (HADOOP-11876) Refactor code to make it more readable, minor maybePrintStats bug

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

Zoran Dimitrijevic updated HADOOP-11876:
----------------------------------------
    Attachment: HADOOP-11876.patch

> Refactor code to make it more readable, minor maybePrintStats bug
> -----------------------------------------------------------------
>
>                 Key: HADOOP-11876
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11876
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: tools/distcp
>    Affects Versions: 3.0.0
>            Reporter: Zoran Dimitrijevic
>            Assignee: Zoran Dimitrijevic
>            Priority: Trivial
>         Attachments: HADOOP-11876.patch
>
>
> This is related to HADOOP-11827 patch from few days ago. I've noticed a minor bug in maybePrintStats logic which is called only when new directory is processed, and prints every 100K objects (effectively, there is a very low probability it'll ever print stats). The reason for this bug is that I was previously printing stats for every new directory, and later decided it's nicer to print stats for large number of new "objects" (files or directories) instead. 
> This is a minor issue - and since I'm refactoring this I've also changed the minor retry logic to make code nicer and more readable.



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