[
https://issues.apache.org/jira/browse/HDFS-9170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934102#comment-14934102
]
Haohui Mai commented on HDFS-9170:
----------------------------------
There are two options that are available:
(1) Move libhdfs, fuse-dfs, and libwebhdfs to {{hadoop-hdfs-client}} but leaves
the unit tests that involves {{MiniDFSCluster}} in {{hadoop-hdfs}}. This is
consistent with what we have done in the Java implementation but also separates
the tests from the real implementation.
(2) Move libhdfs, fuse-dfs, and libwebhdfs to a separate
{{hadoop-hdfs-native-client}} module. It has the benefits of putting both the
implementation and the tests together but it requires several tricks on cmake
and pom to get things to work.
Thoughts? [~cmccabe], do you have any ideas on this?
> 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)
