hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12973) make DU pluggable
Date Thu, 07 Apr 2016 18:21:25 GMT

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

Colin Patrick McCabe commented on HADOOP-12973:

bq. It makes it more obvious when someone overrides the class where things are.

Hmm.  How about making the class {{final}} instead?

Re: DU versus WindowsDU. If you really want to separate the classes, I don't object, but I
don't want the WindowsDU to be a subclass of the Linux DU.  That is just weird.

bq. Shutdown is needed. So it's very strange to have a shutdown without a start.

There is a start-- in GetSpaceUsedBuilder.  Having an "init" method is an anti-pattern.

> make DU pluggable
> -----------------
>                 Key: HADOOP-12973
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12973
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>         Attachments: HADOOP-12973v0.patch, HADOOP-12973v1.patch, HADOOP-12973v10.patch,
HADOOP-12973v2.patch, HADOOP-12973v3.patch, HADOOP-12973v5.patch, HADOOP-12973v6.patch, HADOOP-12973v7.patch,
HADOOP-12973v8.patch, HADOOP-12973v9.patch
> If people are concerned about replacing the call to DU. Then an easy first step is to
make it pluggable. Then it's possible to replace it with something while leaving the default

This message was sent by Atlassian JIRA

View raw message