I've been intermittently backporting things to it, but like you say: not getting much active use.
1. I'd like to view the 3.1 branch as the main "ready to play with" Hadoop 3.x release, with 3.2 some new features. 2. I'm planning on backporting some of the hadoop 3.x ABFS and S3A work to that 3.x release, and for S3A, some to 3.1.x (and indeed, maybe we should do the abfs connector, After all: it's not going to cause any regressions). 3. The hadoop-aws changes will include HADOOP-16117, AWS SDK update - Sean Mackrory has been advocating "keep all active branches current with the AWS SDKs", and I've come to agree. The testing there didn't find any regressions, which was a pleasant surprise. 4. For S3A, a big patch has just gone in, HADOOP-16085, which adds etag and version columns to the S3Guard DDB tables, and uses these at load time. Even if we don't backport that patch to the 3.1 line, it makes sense for all 3.1.x clients to be updating the DB with the relevant columns as they write it, so that on a mixed-client deployment, everyone keeps the table up to date As usual, help welcome, especially with testing -steve On Fri, May 17, 2019 at 12:15 PM Wei-Chiu Chuang <weic...@apache.org> wrote: > Thanks for initiating the discussion, Akira. > > I've given similar thoughts on the possible EOL of Hadoop branch-3.0 line. > IMHO, I'd love to see HDFS-13596 > <https://issues.apache.org/jira/browse/HDFS-13596> fixed to make it > possible to rolling upgrade from Hadoop 2 to Hadoop 3.0, and then roll > another maint. release before we declare EOL. > > But in all seriousness, with my Cloudera hat on, CDH will soon rebase onto > branch-3.1 so it's unlikely Cloudera can sponsor another 3.0 maint release. > With my Apache hat on, Apache is an all-volunteer organization and we all > act individually, but I am just being realistic that there would not be > much motivation to roll another release in the future. > > Thoughts? > > On Fri, May 17, 2019 at 8:31 AM Akira Ajisaka <aajis...@apache.org> wrote: > > > Hi folks, > > > > In branch-3.0, it is almost a year since 3.0.3 was released. Is there > > any committer who wants to be a release manager of 3.0.4? > > > > If there are no users running Apache Hadoop 3.0.x in production, I'm > > thinking we can stop maintaining branch-3.0. Please let me know there > > are any users running Apache Hadoop 3.0.x. > > > > Any thoughts? > > > > -Akira > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > > For additional commands, e-mail: common-dev-h...@hadoop.apache.org > > > > >
