[jira] [Resolved] (HADOOP-17720) Replace Guava Sets usage by Hadoop's own Sets in hadoop-hdfs-project

[ https://issues.apache.org/jira/browse/HADOOP-17720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takanobu Asanuma resolved HADOOP-17720. --- Fix Version/s: 3.4.0 Resolution: Fixed > Replace Guava Sets usage by Hadoop'

[jira] [Resolved] (HADOOP-17722) Replace Guava Sets usage by Hadoop's own Sets in hadoop-mapreduce-project

[ https://issues.apache.org/jira/browse/HADOOP-17722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takanobu Asanuma resolved HADOOP-17722. --- Fix Version/s: 3.4.0 Resolution: Fixed > Replace Guava Sets usage by Hadoop'

Re: [E] Re: [DISCUSS] Change project style guidelines to allow line length 100

In apache tez, formal line length is 120 characters. So, I recommend 120+ On Mon, May 24, 2021 at 4:46 PM Kihwal Lee wrote: > +1 for the 100 char limit. > But I would have liked 132 columns more. :) > > Kihwal > > On Mon, May 24, 2021 at 1:46 PM Sean Busbey > wrote: > > > Hi folks! > > > > The

Re: [E] Re: [DISCUSS] Change project style guidelines to allow line length 100

+1 for the 100 char limit. But I would have liked 132 columns more. :) Kihwal On Mon, May 24, 2021 at 1:46 PM Sean Busbey wrote: > Hi folks! > > The consensus seems pretty strongly in favor of increasing the line length > limit. Do folks still want to see a formal VOTE thread? > > > > On May 1

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86_64

For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/517/ No changes -1 overall The following subsystems voted -1: blanks pathlen unit xml The following subsystems voted -1 but were configured to be filtered/ignored: cc checkstyle javac javado

Re: [DISCUSS] Change project style guidelines to allow line length 100

Hi folks! The consensus seems pretty strongly in favor of increasing the line length limit. Do folks still want to see a formal VOTE thread? > On May 19, 2021, at 4:22 PM, Sean Busbey wrote: > > Hello! > > What do folks think about changing our line length guidelines to allow for > 100 cha

[GitHub] [hadoop-thirdparty] jojochuang opened a new pull request #18: HADOOP-17730. Add back error_prone

jojochuang opened a new pull request #18: URL: https://github.com/apache/hadoop-thirdparty/pull/18 Tested by compiling Ozone with the modified Hadoop-thirdparty 1.1.0 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use th

[jira] [Created] (HADOOP-17730) [thirdparty] Do not exclude error_prone

Wei-Chiu Chuang created HADOOP-17730: Summary: [thirdparty] Do not exclude error_prone Key: HADOOP-17730 URL: https://issues.apache.org/jira/browse/HADOOP-17730 Project: Hadoop Common Iss

Re: [DISCUSS] which release lines should we still consider actively maintained?

+1, to mark 3.1.x EOL. Apache Hive does depends on 3.1.0 as of now, but due to guave upgrade on branch-3.1, the attempt to migrate to latest 3.1.x didn’t work for me atleast couple of months back. So, mostly 3.3.1 would be the only option replacing 3.1.0 there or at worst 3.3.2 in a couple of mo

Re: [DISCUSS] which release lines should we still consider actively maintained?

+1 to EOL 3.1.x at least. > On May 23, 2021, at 9:51 PM, Wei-Chiu Chuang > wrote: > > Sean, > > For reasons I don't understand, I never received emails from your new > address in the mailing list. Only Akira's response. > > I was just able to start a thread like this. > > I am +1 to EOL 3.1

[VOTE] Release Apache Hadoop 3.3.1 - RC1

Hi community, This is the release candidate RC1 of Apache Hadoop 3.3.1 line. All blocker issues have been resolved. It contains 697 fixed jira issues [2] since 3.3.0 which include a lot of features and improvements(read the full set of release notes). Below feature additions are the highlights o

[jira] [Resolved] (HADOOP-17666) Update LICENSE for 3.3.1

[ https://issues.apache.org/jira/browse/HADOOP-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang resolved HADOOP-17666. -- Fix Version/s: 3.4.0 3.3.1 Resolution: Fixed > Update LICEN

[jira] [Resolved] (HADOOP-17670) S3AFS and ABFS to log IOStats at DEBUG mode or optionally at INFO level in close()

[ https://issues.apache.org/jira/browse/HADOOP-17670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-17670. - Fix Version/s: 3.3.2 Resolution: Fixed > S3AFS and ABFS to log IOStats at DEBUG

[jira] [Resolved] (HADOOP-17705) S3A to add Config to set AWS region

[ https://issues.apache.org/jira/browse/HADOOP-17705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-17705. - Fix Version/s: 3.3.2 Resolution: Fixed merged to trunk and branch-3.3. Which I t

[jira] [Created] (HADOOP-17729) Datanode client is stuck, waiting for connections map to be empty

Kiran Kumar Maturi created HADOOP-17729: --- Summary: Datanode client is stuck, waiting for connections map to be empty Key: HADOOP-17729 URL: https://issues.apache.org/jira/browse/HADOOP-17729 Pro

[jira] [Reopened] (HADOOP-17669) Port HADOOP-17079, HADOOP-17505 to branch-3.3

[ https://issues.apache.org/jira/browse/HADOOP-17669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang reopened HADOOP-17669: -- Looking at HADOOP-17079, there are a number of known bugs in the code. Revert it from 3.

[jira] [Reopened] (HADOOP-16752) ABFS: test failure testLastModifiedTime()

[ https://issues.apache.org/jira/browse/HADOOP-16752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran reopened HADOOP-16752: - > ABFS: test failure testLastModifiedTime() > - > >