Depends on your hadoop version, the latest is hadoop.mapreduce, while
hadoop.mapred has been deprecated.Earlier to 0.20.1 use mapred, otherwise using
mapreduce.
API here : http://hadoop.apache.org/common/docs/r0.20.1/api/index.html. Thanks!
On 11/26/09 1:27 AM, "Sangmin Lee" wrote:
Hi all,
I
Provide a description in the exception when an error is encountered parsing
umask
-
Key: HADOOP-6396
URL: https://issues.apache.org/jira/browse/HADOOP-6396
Project: Hadoo
Inconsistent versions of libraries are being included
-
Key: HADOOP-6395
URL: https://issues.apache.org/jira/browse/HADOOP-6395
Project: Hadoop Common
Issue Type: Bug
Reporter:
Helper class for FileContext tests
--
Key: HADOOP-6394
URL: https://issues.apache.org/jira/browse/HADOOP-6394
Project: Hadoop Common
Issue Type: Improvement
Reporter: Jitendra Nath Pandey
+1
I am in favor of committing this to 0.21 because imo it is
not a new HDFS feature but rather an improvement of web UI.
Allen Wittenauer wrote:
> Then you'll have no issues patching other things in 0.21 that are actual
> bug fixes that also meet this criteria, right? Or does this only appl
Allow master to run on larger EC2 instance
--
Key: HADOOP-6393
URL: https://issues.apache.org/jira/browse/HADOOP-6393
Project: Hadoop Common
Issue Type: New Feature
Components: contrib/ec2
Hi Allen,
I guess the "you" in your questions are referring me. My answers are yes and
no, respectively.
Actually, we could possibly commit the patch to ydist, like what we does for
yahoo-hadoop-0.20. It is not a big difference.
BTW, as a cluster administrator, do you think that HDFS-758 is
Run namenode and jobtracker on separate EC2 instances
-
Key: HADOOP-6392
URL: https://issues.apache.org/jira/browse/HADOOP-6392
Project: Hadoop Common
Issue Type: New Feature
Comp
Then you'll have no issues patching other things in 0.21 that are actual
bug fixes that also meet this criteria, right? Or does this only apply to
things that Yahoo! is hitting/deemed worthy?
On 11/25/09 12:03 PM, "Tsz Wo (Nicholas), Sze"
wrote:
> +1 on committing it to 0.21
>
> I also a
+1 on committing it to 0.21
I also agree that it does not impact the 0.21 release since the patch is
already done. The argument of not committing it to 0.21 would be either (1)
the patch is not safe, or (2) the patch is not that useful. I don't see they
are the cases here.
Nicholas Sze
-
Hi all,
I was wondering what is the difference between hadoop.mapreduce package and
hadoop.mapred package.
Seems like mapreduce is replacing mapred.. am I correct here?
If so, which one should I use?
And I don't know how to use API of mapreduce.
Can anyone help me out of this?
Thanks,
Sangmin
We have had several issues with decommissioning in recent past.
Decommissioning takes long time and operations guys have no means to find
out what is taking so long. This is a change in the namenode web UI that
will greatly help hadoop users to monitor the status of decommissioning and
to discove
+1. Backporting this does not in any way impact the release of 21.
-Jakob
Hairong Kuang wrote:
+1. Although this is a new feature, I'd like to have it committed to 0.21
since we have so many issues with delayed decomission recently.
Hairong
On 11/24/09 6:06 PM, "Suresh Srinivas" wrote:
+1
-1
We're never going to see 0.21 if features keep getting backported.
On 11/24/09 9:44 PM, "Owen O'Malley" wrote:
> +1 This sounds like useful information that will and has aided debugging.
>
> -- Owen
+1. Although this is a new feature, I'd like to have it committed to 0.21
since we have so many issues with delayed decomission recently.
Hairong
On 11/24/09 6:06 PM, "Suresh Srinivas" wrote:
> +1. This will also help debug the issues when decommissioning takes a long
> time to complete.
>
>
Classpath should not be part of command line arguments
--
Key: HADOOP-6391
URL: https://issues.apache.org/jira/browse/HADOOP-6391
Project: Hadoop Common
Issue Type: Bug
Components
16 matches
Mail list logo
