ARM Build Details :
https://builds.apache.org/job/Hadoop-qbt-linux-ARM-trunk/202/
CHANGES
[May 18, 2020 6:36:20 AM] (aajisaka) HADOOP-17042. Hadoop distcp throws 'ERROR:
Tools helper
[May 18, 2020 7:29:07 AM] (aajisaka) Revert "YARN-9
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/145/
[May 18, 2020 6:36:20 AM] (Akira Ajisaka) HADOOP-17042. Hadoop distcp throws
'ERROR: Tools helper ///usr/lib/hadoop/libexec/tools/hadoop-distcp.sh was not
found'. Contributed by Aki Tanaka.
+1
On Mon, May 18, 2020 at 12:37 AM Elek, Marton wrote:
>
>
> > One question, for the committers who contributed to Ozone before and got
> > the committer-role in the past (like me), will they carry the
> > committer-role to the new repo?
>
>
> In short: yes.
>
>
> In more details:
>
> This disc
ProtobufHelper should not be a public API. Hadoop uses protobuf
serialization to expertise RPC performance with many drawbacks. The
generalized object usually require another indirection to map to usable
Java object, this is making Hadoop code messy, and that is topic for
another day. The main c
hemanthboyina created HDFS-15362:
Summary: FileWithSnapshotFeature#updateQuotaAndCollectBlocks
should collect all distinct blocks
Key: HDFS-15362
URL: https://issues.apache.org/jira/browse/HDFS-15362
[
https://issues.apache.org/jira/browse/HDFS-15202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei-Chiu Chuang resolved HDFS-15202.
Fix Version/s: 3.4.0
Resolution: Fixed
> HDFS-client: boost ShortCircuit Cache
> ---
For more details, see
https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/689/
[May 17, 2020 3:59:10 AM] (yqlin) HDFS-15264. Backport Datanode detection to
branch-2.10. Contributed by
-1 overall
The following subsystems voted -1:
asflicense findbugs hadolint pathlen un
Rungroj Maipradit created HDFS-15361:
Summary: Implement clear method in ErasureCodingPolicyManager class
Key: HDFS-15361
URL: https://issues.apache.org/jira/browse/HDFS-15361
Project: Hadoop HDFS
One question, for the committers who contributed to Ozone before and got
the committer-role in the past (like me), will they carry the
committer-role to the new repo?
In short: yes.
In more details:
This discussion (if there is an agreement) should be followed by a next
discussion + vot