[ https://issues.apache.org/jira/browse/HDFS-9207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953725#comment-14953725 ]
Haohui Mai commented on HDFS-9207: ---------------------------------- bq. If we can have HDFS-8766 landed before we do the rebase, it will save the re-work on that code that has been kicked around for a month. If James Clampffer can get the gmock stuff for HDFS-8766 done by tomorrow, let's get it reviewed and landed, then land HDFS-9207, then continue to progress on the rest of the outstanding issues. I'm trying to understand why rebasing is an issue at all? It should be a simple {{mv}} command. Am I missing something? I don't think it is a good idea to commit HDFS-8766 with a copy with {{hdfs.h}}. This main motivation of this jira is to avoid duplicating such a copy. bq. I think there is a legitimate need to have the library itself (as opposed to the tests) build without a dependency on the JNI code, but we can leave that as-is for now and make another Jira to capture that work. Just to clarify that the library does not require JNI at all (as this is the main purpose of building this library). > Move the implementation to the hdfs-native-client module > -------------------------------------------------------- > > Key: HDFS-9207 > URL: https://issues.apache.org/jira/browse/HDFS-9207 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: hdfs-client > Reporter: Haohui Mai > Assignee: Haohui Mai > Attachments: HDFS-9207.000.patch > > > The implementation of libhdfspp should be moved to the new hdfs-native-client > module as HDFS-9170 has landed in trunk and branch-2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)