so we would require a specific patch release of Hadoop as a minimum? It's messy, but we've certainly done it before.
On Thu, Feb 17, 2022 at 1:31 PM Andrew Purtell <apurt...@apache.org> wrote: > On Thu, Feb 17, 2022 at 10:50 AM Steve Loughran <ste...@apache.org> wrote: > > > j > > On 2022/02/15 22:27:50 Andrew Purtell wrote: > > > > > The primary consideration to my mind is the state of S3A: in what > > version it can be said to be stable and feature complete. I think 3.3 is > > the appropriate code line for that criteria but perhaps 3.2 could serve > as > > well. > > > > 3.3.1. i have not been near 3.2.x for many years except for a change for > > it to be ok with people disabling dir marker deletion > > (fs.s3a.marker.retention=keep). > > > > 3.3.1 is good, with one little surprise: > > https://issues.apache.org/jira/browse/HADOOP-17771 > > moving to the s3 client builder API for region support (needed for AWS > > AccessPoint VPN access) broke things unless you explicitly set a region, > > were running in EC2 *or had the AWS CLI installed*. All tests running in > > EC2 and all us developers with the CLI installed missed that completely. > > see the jira for the trivial workaround. > > > > > > you need 3.3.1 for up to date abfs connections too. > > > > there's a 3.3.2 release due real soon now...testing the latest RC against > > HBase would be wonderful. > > > > -steve > > > > Thank you for writing in Steve. I think by the time we bring this in for a > landing over here 3.3.2 will be out, that gets my vote. > > -- > Best regards, > Andrew > > Unrest, ignorance distilled, nihilistic imbeciles - > It's what we’ve earned > Welcome, apocalypse, what’s taken you so long? > Bring us the fitting end that we’ve been counting on > - A23, Welcome, Apocalypse >
