Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <0E3EC187-44C6-4B95-B8CD-9E22034B7A71@hortonworks.com>
References: <732DB60A-844D-4FA3-822B-08DB587DEB9B@apache.org>
 <6192A234-0F2E-4CB4-B3C7-142728E0800A@effectivemachines.com>
 <A7EF3127-1DED-46F0-9AA4-A39A3F8DAC98@apache.org> <1471528833445.31857@hortonworks.com>
 <0E3EC187-44C6-4B95-B8CD-9E22034B7A71@hortonworks.com>
From: larry mccay <larry.mccay@gmail.com>
Date: Thu, 18 Aug 2016 12:12:38 -0400
Message-ID: <CACRbFyj=Sv5N6JmyxhdOAL37i0_VmMv85tn6Wis8_OPxRGT6OQ@mail.gmail.com>
Subject: Re: [VOTE] Release Apache Hadoop 2.7.3 RC1
To: Steve Loughran <stevel@hortonworks.com>
Cc: Junping Du <jdu@hortonworks.com>, Vinod Kumar Vavilapalli <vinodkv@apache.org>,
	Allen Wittenauer <aw@effectivemachines.com>,
	"common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>,
	"hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>,
	"yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>,
	"mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>
Content-Type: multipart/alternative; boundary=001a1146ec4ed24f11053a5ad9c6
archived-at: Thu, 18 Aug 2016 16:12:47 -0000

--001a1146ec4ed24f11053a5ad9c6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I believe it was described as some previous audit entries have been
superseded by new ones and that the order may no longer be the same for
other entries.

For what it=E2=80=99s worth, I agree with the assertion that this is a back=
ward
incompatible output - especially for audit logs.

On Thu, Aug 18, 2016 at 11:32 AM, Steve Loughran <stevel@hortonworks.com>
wrote:

>
> > On 18 Aug 2016, at 14:57, Junping Du <jdu@hortonworks.com> wrote:
> >
> > I think Allen's previous comments are very misleading.
> > In my understanding, only incompatible API (RPC, CLIs, WebService, etc.=
)
> shouldn't land on branch-2, but other incompatible behaviors (logs,
> audit-log, daemon's restart, etc.) should get flexible for landing.
> Otherwise, how could 52 issues ( https://s.apache.org/xJk5) marked with
> incompatible-changes could get landed on branch-2 after 2.2.0 release? Mo=
st
> of them are already released.
> >
> > Thanks,
> >
> > Junping
>
>
> Don't get AW started on compatiblity; it'll only upset him.
>
> One thing he does care about is the ability of programs to consume the
> output of commands and logs =E2=80=94and for that even the output of comm=
ands and
> logs need to continue to be parseable
>
> https://hadoop.apache.org/docs/r2.7.1/hadoop-project-dist/hadoop-common/
> Compatibility.html#Command_Line_Interface_CLI
>
> " Changing the path of a command, removing or renaming command line
> options, the order of arguments, or the command return code and output
> break compatibility and may adversely affect users."
>
> I believe Allen is particularly concerned that a minor point release is
> going in as incompatible, on the basis the audit log output will change
> =E2=80=94that's the log that is explicitly designed for machine processin=
g, hooking
> up to flume & kafka, etc. As example, Spotify spoke at a Hadoop Summit
> conference about how they used it to identify files which hadn't been use=
d
> for a long time; inferring an atime attribute from the access history.
>
> What has changed in the output?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>

--001a1146ec4ed24f11053a5ad9c6--