I'm trying to transition jobs off of the yahoo-not-h2 label, but again
I don't see a single label I can use that covers an appropriate set of
nodes.
Can we expand Hadoop to include H10 and H11? Can we come up with a
label that covers both the H* and the physical ubuntu hosts that have
been puppeti
Raul da Silva Martins created HADOOP-13475:
--
Summary: CLONE - Adding Append Blob support for WASB
Key: HADOOP-13475
URL: https://issues.apache.org/jira/browse/HADOOP-13475
Project: Hadoop Comm
Xiao Chen created HADOOP-13474:
--
Summary: Add more details in the log when a token is expired
Key: HADOOP-13474
URL: https://issues.apache.org/jira/browse/HADOOP-13474
Project: Hadoop Common
Iss
I think that incompatible API between 3.0.0-alpha and 3.1.0-beta is something
less confusing than incompatible between 2.8/2.9 and 2.98.x alphas/2.99.x betas.
Why not just follow our previous practice in the beginning of branch-2? we can
have 3.0.0-alpha, 3.1.0-alpha/beta, but once when we are fi
I like the 3.0.0-alphaX approach primarily for simpler understanding of
compatibility guarantees. Calling 3.0.0 alpha and 3.1.0 beta is confusing
because, it is not immediately clear that 3.0.0 and 3.1.0 could be
incompatible in APIs.
I am open to something like 2.98.x for alphas and 2.99.x for be
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/127/
[Aug 7, 2016 9:29:26 PM] (shv) HDFS-10693. metaSave should print blocks, not
LightWeightHashSet.
-1 overall
The following subsystems voted -1:
asflicense unit
The following subsystems voted -1 b
