On 29 July 2014 22:14, Sandy Ryza wrote:
>
> http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/Compatibility.html
Sandy is correct is a semantic compatibility issue. Back then the notion of
"interface" was defined in the early 1970s by D.L Parnas (see:
http://www.cs.mun.ca
Thanks Arpit!
On Tue, Jul 29, 2014 at 2:24 PM, Arpit Agarwal
wrote:
> I cleared out the wiki page and left a forwarding link to the site docs.
> From a quick scan all the content is included in the site docs.
>
>
> On Tue, Jul 29, 2014 at 2:14 PM, Sandy Ryza
> wrote:
>
> > Eli pointed out to m
I cleared out the wiki page and left a forwarding link to the site docs.
>From a quick scan all the content is included in the site docs.
On Tue, Jul 29, 2014 at 2:14 PM, Sandy Ryza wrote:
> Eli pointed out to me that this is the up-to-date compatibility guide:
>
> http://hadoop.apache.org/docs
Eli pointed out to me that this is the up-to-date compatibility guide:
http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/Compatibility.html
Thanks,
Sandy
On Tue, Jul 29, 2014 at 9:39 AM, Sandy Ryza wrote:
> Hi Zhijie,
>
> The Hadoop compatibility guide mentions this as "s
Hi Zhijie,
The Hadoop compatibility guide mentions this as "semantic compatibility":
http://wiki.apache.org/hadoop/Compatibility
My interpretation of the section is that we can't change the behavior of
public APIs unless we're fixing buggy behavior. If the change could break
an existing applicat
Hi folks,
Recently we have a conversation on YARN-2209 about the incompatible changes
over releases. For those API changes that will break binary compatibility,
source compatibility towards the existing API users, we've already had a
rather clear picture about what we should do. However, YARN-2209
