Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A0D79187E9 for ; Wed, 25 Nov 2015 19:24:04 +0000 (UTC) Received: (qmail 40309 invoked by uid 500); 25 Nov 2015 19:24:00 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 40098 invoked by uid 500); 25 Nov 2015 19:24:00 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 40053 invoked by uid 99); 25 Nov 2015 19:24:00 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Nov 2015 19:24:00 +0000 Received: from [10.22.10.88] (unknown [192.175.27.10]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 073891A0015; Wed, 25 Nov 2015 19:23:59 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: [DISCUSS] Looking to a 2.8.0 release From: Vinod Kumar Vavilapalli In-Reply-To: Date: Wed, 25 Nov 2015 11:23:58 -0800 Cc: common-dev@hadoop.apache.org, "yarn-dev@hadoop.apache.org" , "hdfs-dev@hadoop.apache.org" , "mapreduce-dev@hadoop.apache.org" Content-Transfer-Encoding: quoted-printable Message-Id: <1F6C1A76-6C3C-4339-8B4E-D91514BF02B8@apache.org> References: <0C22896E-D77B-4DE4-99A2-9D81E150779C@hortonworks.com> <3505A424-5B02-49FA-9B56-AF13D20FEABD@altiscale.com> To: Allen Wittenauer X-Mailer: Apple Mail (2.2104) There are 40 odd incompatible changes in 3.x: = https://issues.apache.org/jira/issues/?jql=3Dproject%20in%20%28HADOOP%2C%2= 0YARN%2C%20HDFS%2C%20MAPREDUCE%29%20AND%20resolution%20%3D%20Fixed%20AND%2= 0fixVersion%20%3D%203.0.0%20AND%20fixVersion%20not%20in%20%282.6.2%2C%202.= 6.3%2C%202.7.1%2C%202.7.2%2C%202.7.3%2C%202.8.0%29%20and%20%22Hadoop%20Fla= gs%22%20in%20%28%22Incompatible%20change%22%29%20ORDER%20BY%20key%20ASC%2C= %20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC Need to dig deeper on their impact. Clearly all my local shell scripts = completely stopped working, it will be good to have some bridging there = to help users migrate. Like I said before, I will spend more time on trunk only changes in = order to kick-start a 3.x discussion. What are the incompatible changes in the 2.x line that you are talking = about? +Vinod > On Nov 11, 2015, at 2:15 PM, Allen Wittenauer = wrote: >=20 >=20 >> On Nov 11, 2015, at 1:11 PM, Vinod Vavilapalli = wrote: >>=20 >> I=E2=80=99ll let others comment on specific features. >>=20 >> Regarding the 3.x vs 2.x point, as I noted before on other threads, = given all the incompatibilities in trunk it will be ways off before = users can run their production workloads on a 3.x release. >=20 > [citation needed] >=20 > Seriously. Back that statement up especially in light of there = having been more incompatibilities in all the 2.x releases combined than = in 3.x.=20