Thanx Wei-Chiu for the initiative. Definitely makes sense to move to 2.10.x line instead of 2.7, if anyone in the Hadoop ecosystem wants to stay over in 2.x line, it shouldn't be that tough for them to move to 2.10.x from 2.7
+1 to drop Hadoop-3.2, I have heard very few people moving to this release line of hadoop, most probably not many people would be using the 3.2.x release line, so it should be fine to drop. Not sure about the 3.1.x line, I think that is the most adapted hadoop-3 release line, I ever saw. Even for a bunch of downstream projects the 3.1.x line is the most used one, Good to get feedback from folks the way Arpit suggested & if everyone is happy, we can go for it!!! -Ayush On Thu, 27 Jul 2023 at 03:54, Michel Sumbul <michelsum...@gmail.com> wrote: > > Hello, > > I think it make sense to not support anymore 2.x. > > For 3.x I think it really depend of the ecosystem. We need to have a > balance between what allow ozone to quickly iterate and innovative but in > the same time ensure that other open source projects will still work with > newer version of ozone. > I'm particular keen that we ensure the last n version Spark and Trino still > work with the latest version of Ozone. (Over S3 but also HadoopFS > interfaces) > > Without a relatively wide ecosystem Ozone will not succeed as it will be a > barrier to usecase. > > Michel > > Le mer. 26 juil. 2023, 19:00, Arpit Agarwal <aagar...@cloudera.com.invalid> > a écrit : > > > Thanks for starting the discussion Wei-Chiu. It will be good to hear the > > community views on this. Should we also cross-post this topic to GitHub > > discussions and the slack channel for more awareness because this will be > > an impactful change if we go ahead? > > > > > > On Jul 26, 2023 at 10:38:19 AM, Wei-Chiu Chuang <weic...@apache.org> > > wrote: > > > > > Hi Ozoner community, it's me again. > > > > > > I'd like to get your feedback on dropping Hadoop 3.1 3.2 runtime support. > > > > > > Currently, Ozone is built with Hadoop 3.3.6 dependency. Our test matrix > > > certifies Ozone execution with Hadoop 2.7, 3.1, 3.2 and 3.3.6. I am not > > > familiar with the history of this, but given where we are, how do we feel > > > about dropping the test matrix against Hadoop 3.1, 3.2 and 3.3.6? > > > > > > Also Hadoop 2.7 is now at the end of life. If there are still Hadoop 2 > > > users, can we bump to Hadoop 2.10.1 which is the last Hadoop 2 release? > > > > > > I am asking because more and more Ozone features depend on newer Hadoop > > > releases. We have to workaround older releases by various hacks and it's > > > not scalable. As an example, to support unbuffer and bytebuffer-read, we > > > added CapableOzoneFSInputStream that is not in ozonefs-hadoop2. A recent > > > example is HDDS-8436 <https://issues.apache.org/jira/browse/HDDS-8436> > > > where > > > I had to copy several Hadoop classes into Ozone code. > > > > > > Looking forward to hearing from you, > > > Weichiu > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org For additional commands, e-mail: dev-h...@ozone.apache.org
