hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haohui Mai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9170) Move libhdfs / fuse-dfs / libwebhdfs to a separate module
Date Tue, 29 Sep 2015 16:28:04 GMT

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

Haohui Mai commented on HDFS-9170:
----------------------------------

The main benefit that (2) offers is that the implementation and the unit tests reside together,
thus it's slightly easier to maintain. It looks like the benefit is marginal, and (1) sounds
more reasonable then. I'll go with option (1).

> Move libhdfs / fuse-dfs / libwebhdfs to a separate module
> ---------------------------------------------------------
>
>                 Key: HDFS-9170
>                 URL: https://issues.apache.org/jira/browse/HDFS-9170
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Haohui Mai
>            Assignee: Haohui Mai
>
> After HDFS-6200 the Java implementation of hdfs-client has be moved to a separate hadoop-hdfs-client
module.
> libhdfs, fuse-dfs and libwebhdfs still reside in the hadoop-hdfs module. Ideally these
modules should reside in the hadoop-hdfs-client. However, to write unit tests for these components,
it is often necessary to run MiniDFSCluster which resides in the hadoop-hdfs module.
> This jira is to discuss how these native modules should layout after HDFS-6200.



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

Mime
View raw message