hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nigel Daley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1917) Need configuration guides for Hadoop
Date Wed, 31 Oct 2007 21:02:51 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539186

Nigel Daley commented on HADOOP-1917:

Here is feedback on the first half of the mapred tutorial from HADOOP-1917_2_20071031.patch:

"serve as a Tutorial" -> "serve as a tutorial"

up-and-running -> running

parallelly -> in parallel

built of commodity -> built with commodity

which processed -> which are processed

in completely -> in a completely

The frameworks sorts -> The framework sorts

in a FileSystem -> in a filesystem

re-executes the failed ones -> re-execution of the failed ones

Normally, the -> Typically the

Hence the framework -> This configuration enables the framework to

of a master -> of a single master

per node in the cluster -> per cluster node

scheduling the jobs' -> scheduling the job's

interfaces/classes -> interfaces or abstract classes

This, and other facets -> These, and other parameter

&amp; monitoring -> and monitoring (appears in a number of places)

to the job-client etc. -> to the job client. (either remove "etc." or expand it out to
list more items sent to the job client)

make Hadoop Streaming and Hadoop Pipes sentences bullet points.

I haven't compiled the forrest.  Do these type of urls work? 

and/or the reducer. -> and/or the reducer function.

try to avoid <code>interface or class name</code>s (followed by an s).

The <code>key</code>s and <code>value</code>s -> The key and value

Additionally the <code>key</code>s -> Additionally, the key class

have to be -> have to implement (then remove trailing 's' from WritableComparable)

Input &amp; Output -> Input and Output

Lets walk through a simple Map-Reduce application before we jump into details to get a flavour
for how they work. -> 
Before jumping into details, lets walk through a simple Map-Reduce example to get a flavour
for how they work.

WalkThrough -> Walk-through

perhaps you should first talk about what inputs are passed to the map method.

line nos. -> lines (IMO this simplifies the reading)

line no. -> line

line# -> line

output of the each -> output of each 

(same as the -> (the combiner is the same as the

you don't introduce the concept of a combiner -- that may need more explanation (or leave
it out of this tutorial)

(word) -> (or word in this example)

of the program -> method

with the given -> method with the given

interfaces/classes -> interfaces and classes (appears in a number of places in different

> Need configuration guides for Hadoop
> ------------------------------------
>                 Key: HADOOP-1917
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1917
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: conf
>    Affects Versions: 0.14.1
>            Reporter: Sameer Paranjpye
>            Assignee: Arun C Murthy
>            Priority: Critical
>             Fix For: 0.16.0
>         Attachments: HADOOP-1917_1_20071025.patch, HADOOP-1917_2_20071031.patch, HADOOP-1917_3_20071031.patch
> We've recently had a spate of questions on the users list regarding features such as
rack-awareness, the trash can etc. which are not clearly documented from a user/admins perspective.
There is some Javadoc present but most of the "documentation" exists either in JIRA or in
the default config files themselves.
> We should generate top down configuration and use guides for map/reduce and HDFS. These
should probably be in forest and accessible from the project website (Javadoc isn't always
approachable to our non-programmer audience). Committers should look for user documentation
before accepting patches.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message