Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 74400 invoked from network); 19 May 2008 19:24:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 May 2008 19:24:30 -0000 Received: (qmail 27126 invoked by uid 500); 19 May 2008 19:24:30 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 26830 invoked by uid 500); 19 May 2008 19:24:29 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 26819 invoked by uid 99); 19 May 2008 19:24:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 May 2008 12:24:29 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 May 2008 19:23:34 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id A5CC5234C11A for ; Mon, 19 May 2008 12:23:55 -0700 (PDT) Message-ID: <141633485.1211225035678.JavaMail.jira@brutus> Date: Mon, 19 May 2008 12:23:55 -0700 (PDT) From: "Jim Kellerman (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-2916) Refactor src structure, but leave package structure alone In-Reply-To: <156937160.1204250571245.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598052#action_12598052 ] Jim Kellerman commented on HADOOP-2916: --------------------------------------- > Doug Cutting - 19/May/08 11:12 AM > Shouldn't we generally avoid big changes right before a branch? If we want it in 0.17, then we > should do it now, not at the last minute, no? But I still don't see any advantage of doing this > independently of HADOOP2885... -1 on including this in 0.17. It is too radical of a change for a 'patch' release. +1 on including this in 0.18. Hiding implementation is a good idea. > Refactor src structure, but leave package structure alone > --------------------------------------------------------- > > Key: HADOOP-2916 > URL: https://issues.apache.org/jira/browse/HADOOP-2916 > Project: Hadoop Core > Issue Type: Sub-task > Components: dfs > Reporter: Sanjay Radia > Assignee: Raghu Angadi > Attachments: convert-patch.sed, convert-patch.sed, HADOOP-2916.patch, svn-commands.sh, svn-commands.sh > > > This Jira proposes that the src structure be split as below. > The package structure remains the same for this Jira. (Package renaming is part of other JIras such as HADOOP-2885). > The idea is that the src will be split BEFORE the package restructuring > The new proposed src structure is > src/test - unchanged > src/java - will no longer exit , its content will be move to one of core, hdfs, or mapred > src/core - this will contain the core classes that hadoop applications need to link against. > It will contain client side libraries of all fs file systems: local, hdfs, kfs, etc > jar name hadoop_core.jar > src/core/org.apache.hadoop.{conf, fs, filechache, io, ipc, log, metrics, net, record, security, tools, util) > src/core/org.apache.hadoop.dfs - this will contain only the client side parts of dfs. > HADOOP-2885 will rename package dfs to package fs.hdfs > src/hdfs/org.apache.hadoop.dfs - this will contain only the server side of hdfs. > HADOOP-2885 will rename package dfs to package fs.hdfs later; a compatible dfs.DistributedFileSystem will be left for compatibility/ > jar name hadoop_hdfs.jar - this jar can be used to launce NNs and DNs etc. > src/mapred/org.apache.hadoop.mapred.* > Initially one jar: hadoop_mapred.jar > Later this may be split into client-side and server-side jars. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.