The vote passed with the following result.
Binding PMC members:
+1 Chris Nauroth
+1 Ayush Saxena
+1 Steve Loughran
+1 Masatake Iwasaki
Non binding votes:
+1 Viraj Jasani
+1 Ashutosh Gupta
I'm going to publish the artifacts, site docs, maven artifacts, then announce.
Thank you to all who help
+1 binding
I've extended my validator project
https://github.com/steveloughran/validate-hadoop-client-artifacts
it now
* fetches KEYS
* fetches an RC from a remote url
* validates signing
* untars and tries to build source
* untars binary release and tries some native commands
the source build f
+1(non-binding)
* Builds from source look good.
* Checksums and signatures are correct.
* Running basic HDFS and MapReduce commands looks good.
Thanks Masatake.
Thanks & Regards,
Ashutosh
On Fri, May 27, 2022 at 2:15 PM Masatake Iwasaki <
iwasak...@oss.nttdata.co.jp> wrote:
> +1 from myself.
+1,
* Built from source
* Verified Checksums
* Verified Signatures
* Successful RAT check
* Ran some basic HDFS shell commands.
* Browsed through the UI(NN,DN,RM,NM,JHS)
Thanx Masatake for driving the release, Good Luck!!!
-Ayush
On Mon, 30 May 2022 at 03:14, Chris Nauroth wrote:
> +1 (binding
+1 (binding)
* Verified all checksums.
* Verified all signatures.
* Built from source, including native code on Linux.
* mvn clean package -Pnative -Psrc -Drequire.openssl -Drequire.snappy
-Drequire.zstd -DskipTests
* Almost all unit tests passed.
* mvn clean test -Pnative -Dparallel-tests
Thanks for the help, Ayush.
I committed HADOOP-16663/HADOOP-16664 and cherry-picked HADOOP-16985 to
branch-2.10 (and branch-3.2).
If I need to cut RC1, I will try cherry-picking them to branch-2.10.2
Masatake Iwasaki
On 2022/05/28 5:23, Ayush Saxena wrote:
The checksum stuff was addressed in
Sounds good, yes they both are not blocker issues for release anyways
(hence +0), just wanted to get more insights. Thanks for the detailed
clarifications Ayush!
Changing my vote to +1 (non-binding).
On Fri, May 27, 2022 at 1:24 PM Ayush Saxena wrote:
> The checksum stuff was addressed in HADO
The checksum stuff was addressed in HADOOP-16985, so that filename stuff is
sorted only post 3.3.x
BTW it is a known issue:
https://issues.apache.org/jira/browse/HADOOP-16494?focusedCommentId=16927236&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16927236
Must not
+0 (non-binding),
* Signature/Checksum looks good, though I am not sure where
"target/artifacts" is coming from for the tars, here is the diff (this was
the case for 2.10.1 as well but checksum was correct):
1c1
< SHA512 (hadoop-2.10.2-site.tar.gz) =
3055a830003f5012660d92da68a317e15da5b73301c2c7
+1 from myself.
* launched pseudo distributed cluster including kms and httpfs with Kerberos
and SSL enabled.
* created encryption zone, put and read files via httpfs.
* ran example MR wordcount over encryption zone.
* skimmed the contents of site documentation.
* built HBase 1.5.0, Hive 2
Hi all,
Here's Hadoop 2.10.2 release candidate #0:
The RC is available at:
https://home.apache.org/~iwasakims/hadoop-2.10.2-RC0/
The RC tag is at:
https://github.com/apache/hadoop/releases/tag/release-2.10.2-RC0
The Maven artifacts are staged at:
https://repository.apache.org/content/rep
11 matches
Mail list logo
