I don't think we can drop support like that for minors per our compatibility guidelines. I don't know how many run 2.7 or 2.8 in production. We use 2.7 so for our own sake I'm -1 on this proposal. However we could change the default 2.x version we build against to 2.9.2. Shall we discuss that ?
I have no opinion on what should be the default build profile for branch-2. For branch-1 it needs to stay at 2.x for now as I am not able to build it successfully with the 3.x profile. I think it is also pretty unlikely someone will opt to use our 1.x with Hadoop 3. We could ask. Even still, let's be conservative with 1.x, please. > On Jan 25, 2019, at 5:27 AM, 张铎(Duo Zhang) <[email protected]> wrote: > > I think we can drop the support of 2.7.x and 2.8.x when releasing 2.2.0 and > 1.5.0? > > And is it the time to change our default building profile from hadoop2 to > hadoop3? > > Andrew Purtell <[email protected]> 于2019年1月25日周五 上午11:22写道： > >> We could see what 2.9.2 looks like in terms of suitability and stability. >> Is there any reason to look at 2.8 instead of jumping directly to 2.9? >> >> >>> On Thu, Jan 24, 2019 at 1:33 PM Sean Busbey <[email protected]> wrote: >>> >>> heads up that the Apache Hadoop project is discussing marking their 2.7 >>> release line as EOL: >>> >>> https://s.apache.org/Nm83 >>> >>> Hadoop 2.7.1+ is the most recent Hadoop release line to get the "(y)" >>> marker in our Hadoop matrix for HBase branches-1. It's also the earliest >>> Hadoop release line to get the same for our HBase branches-2. >>> >>> If folks want to weigh in on that discussion, now's the time. What, if >>> anything, do we as a community want to do to prepare for when it >> eventually >>> happens? >>> >> >> >> -- >> Best regards, >> Andrew >> >> Words like orphans lost among the crosstalk, meaning torn from truth's >> decrepit hands >> - A23, Crosstalk >>
