jar
> file is execute it.
>
> -RR
> --
> Date: Tue, 15 Apr 2014 13:03:53 -0700
>
> Subject: Re: Doubt regarding Binary Compatibility\Source Compatibility
> with old *mapred* APIs and new *mapreduce* APIs in Hadoop
> From: zs...@hortonworks.com
&
5 Apr 2014 13:03:53 -0700
Subject: Re: Doubt regarding Binary Compatibility\Source Compatibility with old
*mapred* APIs and new *mapreduce* APIs in Hadoop
From: zs...@hortonworks.com
To: user@hadoop.apache.org
1. If you have the binaries that were compiled against MRv1 mapred libs, it
should just
ded?
>
> -RR
>
> > Date: Mon, 14 Apr 2014 10:37:56 -0400
> > Subject: Re: Doubt regarding Binary Compatibility\Source Compatibility
> with old *mapred* APIs and new *mapreduce* APIs in Hadoop
> > From: john.meag...@gmail.com
> > To: user@hadoop.apache.org
>
> &
10:37:56 -0400
> Subject: Re: Doubt regarding Binary Compatibility\Source Compatibility with
> old *mapred* APIs and new *mapreduce* APIs in Hadoop
> From: john.meag...@gmail.com
> To: user@hadoop.apache.org
>
> Also, "Source Compatibility" also means ONLY a recompi
Also, "Source Compatibility" also means ONLY a recompile is needed.
No code changes should be needed.
On Mon, Apr 14, 2014 at 10:37 AM, John Meagher wrote:
> Source Compatibility = you need to recompile and use the new version
> as part of the compilation
>
> Binary Compatibility = you can take s
Source Compatibility = you need to recompile and use the new version
as part of the compilation
Binary Compatibility = you can take something compiled against the old
version and run it on the new version
On Mon, Apr 14, 2014 at 9:19 AM, Radhe Radhe
wrote:
> Hello People,
>
> As per the Apache s