For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/220/
[Jul 30, 2020 4:01:22 AM] (noreply) MAPREDUCE-7051. Fix typo in
MultipleOutputFormat (#338)
[Jul 30, 2020 3:30:22 PM] (ericp) YARN-1529: Add Localization overhead metrics
to NM. Contributed by
Hi Eric and Carlo,
Thanks for taking the initiative! I am willing to take this task up for
improving the Ozone codebase.
I have cloned the task and sub-tasks for Ozone -
https://issues.apache.org/jira/browse/HDDS-4050
- Vivek Subramanian
On Thu, Jul 30, 2020 at 3:54 PM Eric Badger
wrote:
>
Thanks for the responses, Jon and Carlo!
It makes sense to me to prevent future patches from re-introducing the
terminology. I can file a JIRA to add the +1/-1 functionality to the
precommit builds.
As for splitting up the work, I think it'll probably be easiest and
cleanest to have an umbrella
Vivek Ratnavel Subramanian created HADOOP-17172:
---
Summary: Remove non-inclusive terminology from Ozone
Key: HADOOP-17172
URL: https://issues.apache.org/jira/browse/HADOOP-17172
Project:
Vivek Ratnavel Subramanian created HADOOP-17173:
---
Summary: CLONE - Remove whitelist/blacklist terminology from Hadoop
Key: HADOOP-17173
URL: https://issues.apache.org/jira/browse/HADOOP-17173
Thanks again Eric for leading the charge. As for whether to chop it up or
keep it in fewer patches, I think it primarily impact the conflict surface
with dev branches and other in-flight development. More patches are likely
creating more localized clashes (as in I clash with a smaller patch, which
Rodney Aaron Stainback created HADOOP-17171:
---
Summary: Please fix CVEs by removing reference to htrace-core4
Key: HADOOP-17171
URL: https://issues.apache.org/jira/browse/HADOOP-17171
I have created https://issues.apache.org/jira/browse/HADOOP-17168 to remove
non-inclusive terminology from Hadoop. However I would like input on how to
go about putting up patches. This umbrella JIRA is under Hadoop Common, but
there are sure to be instances in YARN, HDFS, and Mapreduce. Should I
Eric Badger created HADOOP-17170:
Summary: Remove master/slave terminology from Hadoop
Key: HADOOP-17170
URL: https://issues.apache.org/jira/browse/HADOOP-17170
Project: Hadoop Common
Issue
Eric Badger created HADOOP-17169:
Summary: Remove whitelist/blacklist from Hadoop
Key: HADOOP-17169
URL: https://issues.apache.org/jira/browse/HADOOP-17169
Project: Hadoop Common
Issue Type:
Eric Badger created HADOOP-17168:
Summary: Remove non-inclusive terminology from Hadoop
Key: HADOOP-17168
URL: https://issues.apache.org/jira/browse/HADOOP-17168
Project: Hadoop Common
Issue
Steve Loughran created HADOOP-17167:
---
Summary: ITestS3AEncryptionWithDefaultS3Settings fails if default
bucket encryption != KMS
Key: HADOOP-17167
URL: https://issues.apache.org/jira/browse/HADOOP-17167
RE Mentorship: I think the Mentorship program is an interesting idea. The
concerns with these efforts is always the follow-through. If you can find a
group of folks that are motivated and will work on this I think it could be
a great idea, especially if you focus on a diverse set of mentees, and
Bilahari T H created HADOOP-17166:
-
Summary: ABFS: Add configs for maxConcurrentRequestCount and
threadpool queue size
Key: HADOOP-17166
URL: https://issues.apache.org/jira/browse/HADOOP-17166
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/10/
No changes
-1 overall
The following subsystems voted -1:
asflicense findbugs hadolint jshint pathlen unit xml
The following subsystems voted -1 but
were configured to be
Sandeep Guggilam created HADOOP-17164:
-
Summary: UGI loginUserFromKeytab doesn't set the last login time
Key: HADOOP-17164
URL: https://issues.apache.org/jira/browse/HADOOP-17164
Project: Hadoop
16 matches
Mail list logo
