Actually, its the other way around (thanks Sandy for catching this
error in my post). The presence of mapreduce.map|reduce.java.opts
overrides mapred.child.java.opts, not the other way round as I had
stated earlier (below).
On Wed, Dec 4, 2013 at 1:28 PM, Harsh J ha...@cloudera.com wrote:
Yes
@Harsh J
Thank you, I intend to upgrade from Hadoop 1.0.4 and this kind of information
is very helpful.
Best regards,
Henry
-Original Message-
From: Harsh J [mailto:ha...@cloudera.com]
Sent: Wednesday, December 04, 2013 4:20 PM
To: user@hadoop.apache.org
Subject: Re: about hadoop-2.2.0
Yes but the old property is yet to be entirely removed (removal of
configs is graceful).
These properties were introduced to provide more fine-tuned way to
configure each type of task separately, but the older value continues
to be accepted if present; the current behaviour is that if the MR