Hi Andrew,
Thank you for all the hard work. I am really excited to see us making progress
towards a 3.0 release.
+1 (Non-Binding)
1. Deployed the downloaded bits on 4 node cluster with 1 Namenode and 3
datanodes.
2. Verified all normal HDFS operations like create directory, create file ,
del
Discovered 1 missing license using the script verify-license-notice.sh.
Missing LICENSE!
./../hadoop-dist/target/hadoop-3.0.0-alpha2/share/hadoop/client/hadoop-client-api-3.0.0-alpha2.jar
- Verified checksums and signatures of the tarballs
- Built source with Java 1.8.0_66 on Mac
- Deployed a pseu
Thanks for great feedback thus far.
I agree with some that this is more of a guideline than a policy. I also
agree to some extent that this is not very enforceable given the current
practice.
I do differ, though, on whether there is value in something like this if it
is not completely enforceable
After some googling, I discovered we need the sign profile to make deploy
work:
mvn deploy -Psign -DskipTests -DskipShading
Updated HowToRelease accordingly.
On Fri, Jan 20, 2017 at 11:15 AM, Andrew Wang
wrote:
> What I meant is that you can mvn deploy the specific missing files to fix
> up th
Hi all,
With heartfelt thanks to many contributors, the RC0 for 3.0.0-alpha2 is
ready.
3.0.0-alpha2 is the second alpha in the planned 3.0.0 release line leading
up to a 3.0.0 GA. It comprises 857 fixes, improvements, and new features
since alpha1 was released on September 3rd, 2016.
More inform
Allen Wittenauer created HDFS-11356:
---
Summary: figure out what to do about
hadoop-hdfs-project/hadoop-hdfs/src/main/native
Key: HDFS-11356
URL: https://issues.apache.org/jira/browse/HDFS-11356
Proje
Chen Liang created HDFS-11355:
-
Summary: Block Storage : merge configuration into ozone
configuration classes
Key: HDFS-11355
URL: https://issues.apache.org/jira/browse/HDFS-11355
Project: Hadoop HDFS
If you ran mvn clean at any point in your repo between create-release and mvn
deploy, you'll need to start at running create-release again. create-release
leaves things in a state that mvn deploy should be ready to go, with no clean
necessary.
> On Jan 20, 2017, at 11:12 AM, Junping Du wrote
What I meant is that you can mvn deploy the specific missing files to fix
up the repo state. Though we should also figure out why the deploy plugin
didn't pick up the signature files the first time.
Best,
Andrew
On Fri, Jan 20, 2017 at 11:12 AM, Junping Du wrote:
> Yes. I did maven deploy in ro
Yes. I did maven deploy in root directory before close the staging repository.
If this is the only suspect, I can drop the repository and do mvn deploy again.
Thanks,
Junping
From: Andrew Wang
Sent: Friday, January 20, 2017 10:48 AM
To: Junping Du
Cc: common-
You can check the error message by clicking on it, a bunch like this:
Missing Signature:
'/org/apache/hadoop/hadoop-mapreduce-client-jobclient/2.8.0/hadoop-mapreduce-client-jobclient-2.8.0-tests.jar.asc'
does not exist for 'hadoop-mapreduce-client-jobclient-2.8.0-tests.jar'.
Did you maven deploy
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/292/
[Jan 19, 2017 7:38:20 AM] (lei) HDFS-11287. Storage class member storageDirs
should be private to avoid
[Jan 19, 2017 8:24:11 AM] (wang) HDFS-110268. Correctly reconstruct erasure
coding file from FSImage.
Surendra Singh Lilhore created HDFS-11354:
-
Summary: TestBlockScanner#testAppendWhileScanning should shutdown
the cluster after test execution
Key: HDFS-11354
URL: https://issues.apache.org/jira/browse/HDF
Yiqun Lin created HDFS-11353:
Summary: Speed the unit tests relevant to DataNode volume failure
testing
Key: HDFS-11353
URL: https://issues.apache.org/jira/browse/HDFS-11353
Project: Hadoop HDFS
Hi,
I have successfully built the release bit on branch-2.8.0 by following:
https://wiki.apache.org/hadoop/HowToRelease step by step. However, when try to
close the "Staging Repositories" at Nexus page
(https://repository.apache.org/#stagingRepositories), I found our repository -
orgapacheh
15 matches
Mail list logo
