accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2854) Bad null check in BulkImport.createNewBulkDir()
Date Fri, 13 Jun 2014 18:33:02 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030969#comment-14030969
] 

Mike Drob commented on ACCUMULO-2854:
-------------------------------------

Yea, there's not any real danger in leaving the null check in. The Path object comes from
Hadoop and is reasonably well-behaved.

> Bad null check in BulkImport.createNewBulkDir()
> -----------------------------------------------
>
>                 Key: ACCUMULO-2854
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2854
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 1.6.0
>            Reporter: Bill Havanki
>            Assignee: Jeffrey S Schwartz
>              Labels: newbie, summit2014
>             Fix For: 1.6.1
>
>         Attachments: ACCUMULO-2854.patch.txt
>
>
> At the beginning of {{createNewBulkDir}} in {{o.a.a.master.tableOps.BulkImport}}:
> {code}
>     String tableDir = fs.matchingFileSystem(new Path(sourceDir), ServerConstants.getTablesDirs()).toString();
>     
>     if (tableDir == null)
>       throw new IllegalStateException(sourceDir + " is not in a known namespace");
> {code}
> The call to {{matchingFileSystem()}} can return null, and if it does, a NullPointerException
will be thrown. {{toString()}} on a non-null result will not return null, so the null check
has no effect.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message