[
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.
