[DISCUSS] Move default Hadoop version to 3.3.x

Hi HBase devs, Over the past few years HBase supports the default Hadoop version of 3.2.x but it also works on Hadoop 3.3.x. I'm wondering if it makes sense to move the current default hadoop.version from 3.2.4 to 3.3.x. Why? 1. From a

Re: [DISCUSS] Move default Hadoop version to 3.3.x

coming back here, I created the https://github.com/apache/hbase/tree/HBASE-27740 and will send PRs accordingly... -Stephen On Thu, Jun 22, 2023 at 3:14 PM Wei-Chiu Chuang wrote: > I am +1 to use a feature branch. > > On Tue, Jun 20, 2023 at 10:20 AM Tak Lon (Stephen) Wu > wrote: > > > or maybe

Re: [DISCUSS] Move default Hadoop version to 3.3.x

In general, in HBase, we will use the last patch release of the oldest supported hadoop release line as our default hadoop dependency. For example, since we claim that 3.x will support hadoop 3.2.x and 3.3.x, then we will declare the default hadoop version as 3.2.4. I think we can discuss whether

Re: [DISCUSS] Move default Hadoop version to 3.3.x

How about using a new hadoop 3.3 profile for features that are explicitly present in 3.3 (like FileSystem changes)? When the time comes, we switch to 3.3 profile by default and drop old hadoop 3 profile that supports 3.2.x versions as of today? On Fri, Jun 16, 2023 at 7:11 AM 张铎(Duo Zhang) wrote

Re: [DISCUSS] Move default Hadoop version to 3.3.x

or maybe we create a new feature branch hadoop-33-ozone that has these interfaces and ozone related support, then we put all the feature changes into this feature branch and merge later? The problem I see is that it's hard and very confusing to maintain two hadoop3 profiles, and I can see sooner o

Re: [DISCUSS] Move default Hadoop version to 3.3.x

I am +1 to use a feature branch. On Tue, Jun 20, 2023 at 10:20 AM Tak Lon (Stephen) Wu wrote: > or maybe we create a new feature branch hadoop-33-ozone that has these > interfaces and ozone related support, then we put all the feature changes > into this feature branch and merge later? > > The p