Is it a blocker? It seems to be an optional test. While it can be
confusing to have 0.6.0 it's very rarely used and the functionality is
tested anyway...
What do you think?
Thanks,
Marton
On 8/24/20 10:01 PM, Attila Doroszlai wrote:
Hi Sammi,
Thanks for creating the RC. I have found that t
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/245/
[Aug 24, 2020 9:30:02 AM] (pjoseph) YARN-10360. Support Multi Node Placement in
SingleConstraintAppPlacementAllocator
[Aug 24, 2020 11:00:35 AM] (Stephen O'Donnell) HADOOP-17209. Erasure Coding:
Nati
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/36/
No changes
-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hado
Hi Sammi,
Thanks for creating the RC. If you do spin up a new RC, could you please
consider including the following 2 Jiras in the release:
HDDS-4068
HDDS-4063
Thanks,
Hanisha
> On Aug 24, 2020, at 1:01 PM, Attila Doroszlai wrote:
>
> Hi Sammi,
>
> Thanks for creating the RC. I have found
Hi Sammi,
Thanks for creating the RC. I have found that there are some leftover
references to version "0.6.0" in upgrade scripts and tests
(HDDS-4139). Created a pull request to fix it, please consider
including it in the release.
thanks,
Attila
On Mon, Aug 24, 2020 at 3:55 PM Elek, Marton wr
Hello everyone!
We are considering migrating to Hadoop 3, and we would be very interested to
hear about your experiences. If you have migrated from Hadoop 2 to Hadoop 3
and can provide insights, please kindly consider attending the following:
Date: Wednesday, Aug 26, 2020
Time: 10:00 A.M. PDT / 1
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/244/
[Aug 23, 2020 10:40:47 AM] (Hemanth Boyina) HDFS-14504. Rename with Snapshots
does not honor quota limit.
-1 overall
The following subsystems voted -1:
asflicense pathlen unit xml
The foll
+1 (binding)
1. verified signatures
2. verified checksums
3. verified the output of `ozone version` (includes the good git revision)
4. verified that the source package matches the git tag
5. verified source can be used to build Ozone without previous state
(docker run -v ... -it maven