+1 (binding)
Thanks to the Ozone folks for their efforts at maintaining good separation
with HDFS and common. I took a lot of heat for the unpopular opinion that
they should be separate, so I am glad the process has worked out well for
both codebases. It looks like my concerns were addressed and
+1 assuming we get the technical issues sorted. I'll give your patch a go
today.
As Steve mentioned on the JIRA, unsupported JVM is called out as an
exception in the compatibility guidelines:
"The JVM requirements will not change across point releases within the same
minor release except if the J
+1. I think formatted patches and PRs will be an improvement. I've used
the git --committer thing a couple of times here without issue.
Another unrelated improvement with github is handling of large changes. I
really think large patches should be split up into logical subcommitts and
PR's support
Thanks Sunil and everyone who has worked on this release.
+1 from me.
- Verified checksums for tar file.
- Built from tar.gz.
- Ran through S3A and S3Guard integration tests (in AWS us-west 2).
This includes a yarn minicluster test but is mostly focused on s3a/s3guard.
Cheers,
Aaron
On Thu, J
achieve the faster release
> cadence
> >>>>>> also.
> >>>>>>
> >>>>>> Thoughts?
> >>>>>>
> >>>>>> - Sunil
> >>>>>>
> >>>>>>
> >>>>>
On Tue, Jul 17, 2018 at 7:21 PM Steve Loughran
wrote:
>
>
> On 16 Jul 2018, at 23:45, Sunil G sun...@apache.org>> wrote:
>
> I would also would like to take this opportunity to come up with a detailed
> plan.
>
> - Feature freeze date : all features should be merged by August 10, 2018.
>
>
>
>
+1
Built from source. Ran S3A integration tests in us-west-2 with S3Guard
(both Local and Dynamo metadatastore).
Everything worked fine except I hit one integration test failure. It is a
minor test issue IMO and I've filed HADOOP-14927
Failed tests:
ITestS3GuardToolDynamoDB>AbstractS3GuardToo
