There are 40 odd incompatible changes in 3.x: https://issues.apache.org/jira/issues/?jql=project%20in%20%28HADOOP%2C%20YARN%2C%20HDFS%2C%20MAPREDUCE%29%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%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%20Flags%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 <a...@altiscale.com> wrote: > > >> On Nov 11, 2015, at 1:11 PM, Vinod Vavilapalli <vino...@hortonworks.com> >> wrote: >> >> I’ll let others comment on specific features. >> >> 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. > > [citation needed] > > 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.
