Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 32205 invoked from network); 6 Mar 2007 21:58:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Mar 2007 21:58:46 -0000 Received: (qmail 25131 invoked by uid 500); 6 Mar 2007 21:58:53 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 25103 invoked by uid 500); 6 Mar 2007 21:58:53 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 25094 invoked by uid 99); 6 Mar 2007 21:58:53 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Mar 2007 13:58:53 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Mar 2007 13:58:44 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4348271409E for ; Tue, 6 Mar 2007 13:58:24 -0800 (PST) Message-ID: <16524048.1173218304272.JavaMail.root@brutus> Date: Tue, 6 Mar 2007 13:58:24 -0800 (PST) From: "Sameer Paranjpye (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Commented: (HADOOP-1069) Rename Hadoop record I/O to Jute In-Reply-To: <12712754.1173204324581.JavaMail.root@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-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478598 ] Sameer Paranjpye commented on HADOOP-1069: ------------------------------------------ These are not bad names, IMO. I didn't have to walk down the list to come up with these, it was the first thought that crossed my mind. FWIW, MapReduce is not a particularly descriptive name. It is a label that has been made popular by the MR paper. If a person hasn't read the paper, hears about Hadoop being a distributed computing platform, and then starts browsing the javadoc - the name 'org.apache.hadoop.mapred' doesn't bring up an image of a cluster performing computation. There are cases where you need descriptive names and cases where you need labels or brands. The latter are by far less common than the former, but they do come up. They are often merited by applications or frameworks, this is such a case. > Rename Hadoop record I/O to Jute > -------------------------------- > > Key: HADOOP-1069 > URL: https://issues.apache.org/jira/browse/HADOOP-1069 > Project: Hadoop > Issue Type: Improvement > Components: record > Affects Versions: 0.12.0 > Environment: All > Reporter: Milind Bhandarkar > Assigned To: Milind Bhandarkar > Fix For: 0.13.0 > > > jute was the original name of the hadoop record i/o component. IMHO, it is easier to pronounce, easier to remember and has already stuck among its users. This renaming should be done while there isn't a large codebase using jute, otherwise it will be very difficult later. rcc will be renamed jrc (jute record compiler). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.