Re: Un-deprecate the old MapReduce API?

[Anthony Urso]

+1

On Wed, Apr 21, 2010 at 2:24 PM, Tom White t...@cloudera.com wrote:
 The old MapReduce API in org.apache.hadoop.mapred was deprecated in
 the 0.20 release series when the new (Context Objects) MapReduce API
 was added in org.apache.hadoop.mapreduce. Unfortunately, the new API
 was not complete in 0.20 and most users stayed with the old API. This
 has led to the confusing situation where the old API is generally
 recommended, even though it is deprecated.

 To remedy this situation I suggest that we remove deprecations from
 the old API in 0.20 and trunk, and mark the new API as Evolving (see
 MAPREDUCE-1623 for the latter). This would mean a few things:

 * The next 0.20 release would have a non-deprecated old API.
 * The forthcoming 0.21 release would have a Stable (non-deprecated)
 old API, and a Evolving new API.
 * For some pre-1.0 release (perhaps 0.22), the old API could be
 deprecated again, and the new API marked as Stable.
 * In the 1.0 release it would be possible to remove the old API.

 Thoughts?

 Tom

Re: How to submit a MapReduce job remotely

[Anthony Urso]

Try something along the lines of

hadoop -jt jobtracker host name jar your jar your main class your
arguments...

Cheers,
Anthony


On Tue, Jul 30, 2013 at 2:49 PM, Adam Iezzi aie...@hotmail.com wrote:

 Currently, when submitting a job to MapReduce,
 I have to build/compile my jar file in my IDE. Then FTP the jar over to the
 jobtracker, so that I can execute it via command line. What I'm wondering
 is if
 there is anyway to submit/run the job remotely? e.g. either from my local
 machine or from a deployed WAR file on remote container.



 If this is possible (I hope it is),
 would anybody be able to point me to a few examples on how this is
 accomplished? I'm using the new MapReduce API.



 Thank you,



 Adam