Re: [VOTE] Release Apache Hadoop Thirdparty 1.3.0

+1 (Binding) * Built from source * Verified Signature(Signed by Mukund) * Verified Checksums * No diff b/w the git tag & src tar * Verified the NOTICE & LICENSE files * Skimmed over the contents of the site jar * Built Hadoop trunk with 1.3.0 version * Checked the hadoop test results here [1], not

Re: [DISCUSS] what needs to be done to switch to java17

> One thing I know is that it is necessary to upgrade JUnit 4 to JUnit 5 Do you know any specific reason or docs mentioning that? Just curious as to why we need to migrate to JUnit 5 for JDK-17, Looking here [1], it seems like it supports JDK-21 as well and even [2] mentions like it does support

Re: [DISCUSS] what needs to be done to switch to java17

Depends on what we mean by switching to JDK-17, Compile time support or Runtime support, We don't have compile time support for JDK-11 too, it is just runtime, We have a daily build as well for JDK-11, which has now some genuine failures now, need to check [1], as of now the version is hardcoded he

Re: [DISCUSS] pruning surplus branches/tags from the main hadoop repo

+1 for the proposal, the first thing might be to just drop the unnecessary branches which are either from dependabot or someone accidentally created a branch in the main repo rather than in their fork, there are many, I don't think we need them in the archived repo either Regarding (3) If you mean

[jira] [Resolved] (MAPREDUCE-7475) Fix non-idempotent unit tests

[ https://issues.apache.org/jira/browse/MAPREDUCE-7475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena resolved MAPREDUCE-7475. - Hadoop Flags: Reviewed Resolution: Fixed > Fix non-idempotent unit te

Re: [ANNOUNCE] New Hadoop Committer - Haiyang Hu

Congratulations Haiyang!!! -Ayush > On 22 Apr 2024, at 9:41 AM, Xiaoqiao He wrote: > > I am pleased to announce that Haiyang Hu has been elected as > a committer on the Apache Hadoop project. We appreciate all of > Haiyang's work, and look forward to her/his continued contributions. > > Congr

Re: [VOTE] Release Apache Hadoop 3.4.0 (RC3)

> Counter should be with yourself vote, where the current summary is 5 +1 binding and 1 +1 non-binding. Let's re-count when deadline. Just on the process: The release manager needs to "explicitly" vote like any other before counting their own vote, there has been a lot of discussions around that

Re: [DISCUSS] Support/Fate of HBase v1 in Hadoop

because > 2.2.x > > is also very old and EOL. 2.5.x is the currently maintained release for > > hbase2, with 2.5.7 being the latest. We’re soon going to release 2.6.0 as > > well. > > > > On Tue, Mar 5, 2024 at 6:56 AM Ayush Saxena wrote: > > > > > Hi Folks,

Re: [VOTE] Release Apache Hadoop 3.4.0 (RC3)

anytime soon I will abstain -Ayush On Thu, 7 Mar 2024 at 08:33, Xiaoqiao He wrote: > cc @Chao Sun @zhang...@apache.org > @Ayush Saxena > Would you mind helping to check the upstream systems(Spark, HBase, Hive) > dependency with > the new hadoop release version if necessary? T

[DISCUSS] Support/Fate of HBase v1 in Hadoop

Hi Folks, As of now we have two profiles for HBase: one for HBase v1(1.7.1) & other for v2(2.2.4). The versions are specified over here: [1], how to build is mentioned over here: [2] As of now we by default run our Jenkins "only" for HBase v1, so we have seen HBase v2 profile silently breaking a c

Re: [VOTE] Release Apache Hadoop Thirdparty 1.2.0 (RC1)

h `mvn clean install > -DskipTests` using the thirdparty 1.2.0-RC1 > * There are not any diffs between tag and src > > Regards, > - Takanobu Asanuma > > 2024年2月6日(火) 11:03 Xiaoqiao He : > > > cc @PJ Fanning @Ayush Saxena > @Steve > > Loughran @Takanobu Asanuma

Re: [VOTE] Release Apache Hadoop Thirdparty 1.2.0 RC0

* Built from source * Verified Checksums * Verified Signatures * Validated files have ASF header Not sure if having diff b/w the git tag & src tar is ok, this doesn't look like core code change though, can anybody check & confirm? -Ayush On Thu, 1 Feb 2024 at 13:39, Xiaoqiao He

Re: [VOTE] Release Apache Hadoop 3.4.0 RC0

We should consider including https://issues.apache.org/jira/browse/HDFS-17129 Which looks like inducing some misorder between IBR & FBR which can potentially lead to strange issues, if that can’t be merged, should revert the one which causes that. I think we should check for any ticket which has

Re: Re: [DISCUSS] Release Hadoop 3.4.0

think the release discussion can be in public ML? > > > > Good idea. cc common-dev/hdfs-dev/yarn-dev/mapreduce-dev ML. > > > > Best Regards, > > - He Xiaoqiao > > > > On Tue, Jan 2, 2024 at 6:18 AM Ayush Saxena wrote: > > > > > +1 from me a

Re: [VOTE] Hadoop 3.2.x EOL

+1 -Ayush > On 06-Dec-2023, at 9:40 AM, Xiaoqiao He wrote: > > Dear Hadoop devs, > > Given the feedback from the discussion thread [1], I'd like to start > an official thread for the community to vote on release line 3.2 EOL. > > It will include, > a. An official announcement informs no furt

Re: [DISCUSS] Make some release lines EOL

Thanx He Xiaoqiao for starting the thread. +1 to mark 3.2 EOL. I am not sure about branch-2 stuff, I think a bunch of folks are still using Hadoop 2.x, but we hardly push anything over there & I am not sure if anyone is interested in releasing that or not. > Hadoop 3.3 Release (release-3.3.5 at J

Re: [DISCUSS] Hadoop 3.4.0 release

Hi Ahmar, Makes sense to have a 3.4.0 rather than a 3.3.x if there are major changes. Few things on the process: * trunk should now point to 3.5.0-SNAPSHOT * Fix Versions of all the tickets merged to trunk would be 3.4.0 as of now, you need to move it to 3.5.0, else while chasing the release, the

[jira] [Resolved] (MAPREDUCE-7459) Fixed TestHistoryViewerPrinter flakiness during string comparison

[ https://issues.apache.org/jira/browse/MAPREDUCE-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena resolved MAPREDUCE-7459. - Fix Version/s: 3.4.0 (was: 3.3.6) Hadoop Flags: Reviewed

Re: [ANNOUNCE] New Hadoop PMC Member - Shilun Fan

Congratulations!!! -Ayush > On 31-Oct-2023, at 6:15 PM, Samrat Deb wrote: > > Congratulations Shilun Fan > > Bests, > Samrat > >> On Tue, Oct 31, 2023 at 6:07 PM Tao Li wrote: >> >> Congratulations!!! >> >> Xiaoqiao He 于2023年10月31日周二 20:19写道： >> >>> On behalf of the Apache Hadoop PMC, I

Re: [ANNOUNCE] New Hadoop Committer - Simbarashe Dzinamarira

Congratulations!!! -Ayush > On 03-Oct-2023, at 5:42 AM, Erik Krogen wrote: > > Congratulations Simba! Thanks for the great work you've done on making HDFS > more scalable! > >> On Mon, Oct 2, 2023 at 4:31 PM Iñigo Goiri wrote: >> >> I am pleased to announce that Simbarashe Dzinamarira has b

Re: [ANNOUNCE] New Hadoop Committer - Shuyan Zhang

Congratulations!!! Sent from my iPhone > On 27-Sep-2023, at 9:56 AM, Xiaoqiao He wrote: > > I am pleased to announce that Shuyan Zhang has been elected as > a committer on the Apache Hadoop project. We appreciate all of > Shuyan's work, and look forward to her/his continued contributions. > >

Re: HADOOP-18207 hadoop-logging module about to land

tial num of incompatibilities that would arise with jersey 2 > migration. > > I am really grateful to all reviewers that have reviewed the tasks so far, > I am not expecting reviewers to be able to provide their reviews as quickly > as possible, this particular sub-task has been dev and test ready f

Re: HADOOP-18207 hadoop-logging module about to land

Hi Wei-Chiu, I am glad this activity finally made it to the dev mailing list. Just sharing the context being the guy who actually reverted this last time it was in: It had a test failure on the PR itself and it went in, that had nothing to do with the nature of the PR, generic for all PR and all pr

Re: Signing releases using automated release infra

ue, 18 Jul 2023 at 21:05, Ayush Saxena wrote: >> >> Something we can explore as well!! >> >> -Ayush >> >> Begin forwarded message: >> >> > From: Volkan Yazıcı >> > Date: 19 July 2023 at 1:24:49 AM IST >> > To: d...@communit

Fwd: Signing releases using automated release infra

Something we can explore as well!! -Ayush Begin forwarded message: > From: Volkan Yazıcı > Date: 19 July 2023 at 1:24:49 AM IST > To: d...@community.apache.org > Subject: Signing releases using automated release infra > Reply-To: d...@community.apache.org > > Abstract: Signing release artifac

Re: [VOTE] Release Apache Hadoop 3.3.6 RC1

+1 (Binding) * Built from source (x86 & Arm) * Successful native build on ubuntu 18.04(x86) & ubuntu 20.04(Arm) * Verified Checksums (x86 & Arm) * Verified Signatures (x86 & Arm) * Successful RAT check (x86 & Arm) * Verified the diff b/w the tag & the source tar * Built Ozone with 3.3.6, green bui

Re: [VOTE] Release Apache Hadoop 3.3.6 RC0

Folks you had put your vote on the wrong thread, this is the RC0 thead, you need to put on the RC1, https://lists.apache.org/thread/022p4rml5tvsx9xpq6t7b3n1td8lzz1d -Ayush Sent from my iPhone > On 20-Jun-2023, at 10:03 PM, Ashutosh Gupta > wrote: > > Hi > > Thanks Wei-Chiu for driving the

Re: [VOTE] Release Apache Hadoop 3.3.6 RC0

Hi Masatake, That ticket is just a backport of: https://issues.apache.org/jira/browse/HADOOP-17612 and the only java code change is in test [1], which is causing issues for you. That ticket isn't marked incompatible either, so maybe that is why it got pulled back. btw. the original PR does men

Fwd: Call for Presentations, Community Over Code Asia 2023

Forwarding from dev@hadoop to the ML we use. Original Mail: https://lists.apache.org/thread/3c16xyvmdyvg4slmtfywcwjbck1b4x02 -Ayush -- Forwarded message - From: Rich Bowen Date: Mon, 5 Jun 2023 at 21:43 Subject: Call for Presentations, Community Over Code Asia 2023 To: rbo...@apa

Re: Issues with Github PR integration with Jira

It is sorted now. the github bot got blocked as a spam user. poor fellow :-) -Ayush On Fri, 19 May 2023 at 05:33, Ayush Saxena wrote: > Hi Folks, > Just wanted to let everyone know, there is an ongoing issue with > Github PR & Jira integration since the last few days. > >

Re: Call for Presentations, Community Over Code 2023

r Community over Code Asia 2023 > > https://www.bagevent.com/event/cocasia-2023-EN > Happening Aug 18-20. CfP due by 6/6 > > > On Tue, May 9, 2023 at 8:39 PM Ayush Saxena wrote: >> >> Forwarding from dev@hadoop to the dev ML which we use. >> >> The actua

Issues with Github PR integration with Jira

Hi Folks, Just wanted to let everyone know, there is an ongoing issue with Github PR & Jira integration since the last few days. The Pull Requests aren't getting linked automatically to Jira in some cases, If you observe that Please link manually unless this issue is resolved. I have an INFRA tic

RE: Call for Presentations, Community Over Code 2023

Forwarding from dev@hadoop to the dev ML which we use. The actual mail lies here: https://www.mail-archive.com/dev@hadoop.apache.org/msg00160.html -Ayush On 2023/05/09 21:24:09 Rich Bowen wrote: > (Note: You are receiving this because you are subscribed to the dev@ > list for one or more Apache

Re: Nightly Jenkins CI for Hadoop on Windows 10

hit the timeout -Ayush On Tue, 9 May 2023 at 11:49 PM, Ayush Saxena wrote: > Hi Gautham, > The only advantage I can think of is your limitation to nodes shouldn’t > bother much. Though there are limited resources given to Apache but still > never observed any starvation in any pro

Re: Nightly Jenkins CI for Hadoop on Windows 10

oint and we certainly don't want to > regress > in this regard. I think I'll pursue this once I stabilize the nightly CI > and after > I sort out the rest of the failing parts (mvnsite, javadoc etc). > > Also, does Github Actions provide any advantage over precommit CI? &g

Re: Nightly Jenkins CI for Hadoop on Windows 10

Awesome!!! Do you plan to run some builds per PR to ensure no commits breaks it in the future? Worth exploring GithubActions in the later stages if we can have an action for maven install on windows, it won't affect the normal build time as well. can run in parallel with the existing builds. -Ayu

Re: [DISCUSS] Hadoop 3.3.6 release planning

That openssl change ain't a blocker now from my side, that ABFS-Jdk-17 stuff got sorted out, Steve knew a way out On Sat, 6 May 2023 at 00:51, Ayush Saxena wrote: > > Thanx Wei-Chiu for the initiative, Good to have quick releases :) > > With my Hive developer hat on, I wo

Re: [DISCUSS] Hadoop 3.3.6 release planning

Thanx Wei-Chiu for the initiative, Good to have quick releases :) With my Hive developer hat on, I would like to bring some stuff up for consideration(feel free to say no, if it is beyond scope or feels even a bit unsafe, don't want to mess up the release) * HADOOP-18662: ListFiles with recursive

Re: [VOTE] Release Apache Hadoop 3.3.5 (RC3)

gt; > Steve Loughran > Chris Nauroth > Masatake Iwasaki > Ayush Saxena > Xiaoqiao He > > +1 non-binding > > Viraj Jasani > > > 0 or -1 votes: none. > > > Accordingly: the release is good! > > I will send the formal announcement out tomorrow >

A Message from the Board to PMC members

d...@hadoop.apache.org received a mail from the apache board, forwarding it to the mailing lists which we use, sharing the link here: https://www.mail-archive.com/dev@hadoop.apache.org/msg00158.html private@ in bcc -Ayush - To

Re: [DISCUSS] hadoop branch-3.3+ going to java11 only

hts. Probably bad takes: > > There are projects experimenting with JDK17 now. > JDK11 active support will end in 6 months. If it's already hard to migrate > from JDK8 why not retarget JDK17. > > On Tue, Mar 28, 2023 at 10:30 AM Ayush Saxena wrote: > >> I know Jersey u

Re: [DISCUSS] hadoop branch-3.3+ going to java11 only

I know Jersey upgrade as a blocker. Some folks were chasing that last year during 3.3.4 time, I don’t know where it is now, didn’t see then what’s the problem there but I remember there was some intitial PR which did it for HDFS atleast, so I never looked beyond that… I too had jdk-11 in my min

Fwd: TAC supporting Berlin Buzzwords

Forwarded a recieved. -Ayush -- Forwarded message - From: Gavin McDonald Date: Fri, 24 Mar 2023 at 15:27 Subject: TAC supporting Berlin Buzzwords To: PMCs, Please forward to your dev and user lists. Hi All, The ASF Travel Assistance Committee is supporting taking up to six

Re: [VOTE] Release Apache Hadoop 3.3.5 (RC3)

+1(Binding) * Built from source (x86 & ARM) * Successful Native Build (x86 & ARM) * Verified Checksums (x86 & ARM) * Verified Signature (x86 & ARM) * Checked the output of hadoop version (x86 & ARM) * Verified the output of hadoop checknative (x86 & ARM) * Ran some basic HDFS shell commands. * Ran

Re: [VOTE] Release Apache Hadoop 3.3.5 (RC3)

Count me in as well. I am almost done. So, you have 3 potential votes, can be happy now :) Thanx Steve for the efforts!!! -Ayush > On 19-Mar-2023, at 2:46 AM, Chris Nauroth wrote: > > Yes, I'm in progress on verification, so you can expect to get a vote from > me. Thank you, Steve! > > Chri

Re: [VOTE] Release Apache Hadoop 3.3.5 (RC2)

> > I will highlight that I am completely fed up with doing this release and > really want to get it out the way -for which I depend on support from as > many other developers as possible. hmm, I can feel the pain. I tried to find if there is any config or any workaround which can dodge this HDF

Re: [VOTE] Release Apache Hadoop 3.3.5

> > And i > think we need to change the PR template to mention transitive updates in > the license bit too Not sure if that is gonna help, People might ignore that or check that in overconfidence. No harm though.. BTW Ozone has some cool stuff to handle this, it was added here: https://github.c

[jira] [Resolved] (MAPREDUCE-7428) Fix failures related to Junit 4 to Junit 5 upgrade in org.apache.hadoop.mapreduce.v2.app.webapp

[ https://issues.apache.org/jira/browse/MAPREDUCE-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena resolved MAPREDUCE-7428. - Resolution: Fixed > Fix failures related to Junit 4 to Junit 5 upgrade

[jira] [Reopened] (MAPREDUCE-7428) Fix failures related to Junit 4 to Junit 5 upgrade in org.apache.hadoop.mapreduce.v2.app.webapp

[ https://issues.apache.org/jira/browse/MAPREDUCE-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena reopened MAPREDUCE-7428: - > Fix failures related to Junit 4 to Junit 5 upgrade

Re: yetus reporting javadoc errors on @InterfaceAudience attributes

ush On Tue, 21 Feb 2023 at 21:16, Steve Vaughan wrote: > I'd be happy to take a look at the tests with a fresh set of eyes. Was > there an existing PR for Junit work? > ------ > *From:* Ayush Saxena > *Sent:* Tuesday, February 21, 2023 1:24 AM >

Re: yetus reporting javadoc errors on @InterfaceAudience attributes

toryEvents/testEventsFlushOnStop/ On Fri, 23 Dec 2022 at 08:50, Ayush Saxena wrote: > Have we stopped >> with the java8 builds? > > > Nopes, The answer is here just cross posting: > https://github.com/apache/hadoop/pull/5226#issuecomment-1354964948 > > Regarding dropping Java

Re: [VOTE] Release Apache Hadoop 3.3.5

t > downstream projects have tests that do restarts on a MiniDFSCluster. > > Chris Nauroth > > > On Wed, Jan 4, 2023 at 4:22 PM Ayush Saxena wrote: > > > Hmm I'm looking at HADOOP-11867 related stuff but couldn't find it > >> mentioned anywhere in change

Re: [VOTE] Release Apache Hadoop 3.3.5

> > Hmm I'm looking at HADOOP-11867 related stuff but couldn't find it > mentioned anywhere in change log or release notes. Are they actually > up-to-date? I don't think there is any issue with the ReleaseNotes generation as such but with the Resolution type of this ticket, It ain't marked as Fix

Re: [VOTE] Release Apache Hadoop 3.3.5

Mostly or may be all of those failures are due to HADOOP-18324 , there is a Jira tracking issues with TestLeaseRecovery2 linked to that as well HDFS-16853 -Ayush On Wed, 28 Dec 2022 at 09:13, Vi

Re: exciting new content needed for the 3.3.5 index.md file

Hi Steve, I just went through the Jira's fixed in HDFS[1] Sharing some stuff which I find good enough to find a mention. 1.HDFS-13522 , HDFS-16767 & Related Jiras: Allow Observer Reads in HDFS Route

Re: [DISCUSS] JIRA Public Signup Disabled

, Mingliang Liu wrote: > Thanks Ayush for taking care of this. I think option 1 sounds good. > > > On Nov 22, 2022, at 2:51 PM, Ayush Saxena wrote: > > > > Hi Folks, > > Just driving the attention towards the recent change from Infra, which > > disables new people fr

[DISCUSS] JIRA Public Signup Disabled

Hi Folks, Just driving the attention towards the recent change from Infra, which disables new people from creating a Jira account, in order to prevent spams around JIRA. So, the new Jira account creation request needs to be routed via the PMC of the project. So, we have 2 options, which I can think

2022 ASF Community Survey

Apache community, your opinion matters: we want to hear your voice. If you have any questions about the survey or otherwise, please reach out to us! Kindly, Ayush Saxena On Behalf of: Katia Rojas V.P. of Diversity and Inclusion The Apache Software Foundation

[jira] [Resolved] (MAPREDUCE-7385) impove JobEndNotifier#httpNotification With recommended methods

[ https://issues.apache.org/jira/browse/MAPREDUCE-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena resolved MAPREDUCE-7385. - Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed > imp

Re: [VOTE] Release Apache Hadoop 3.2.4 - RC0

+1(Binding) * Built from Source * Successful native build on Ubuntu 18.04 * Verified Checksums * Verified Signatures * Successful RAT check * Ran Basic HDFS shell commands * Ran basic MR example Jobs (TeraGen/TeraSort & TeraValidate) * Browsed through UI(NN, DN, RM, NM & JHS) * Skimmed through the

[jira] [Resolved] (MAPREDUCE-7389) Typo in description of "mapreduce.application.classpath" in mapred-default.xml

[ https://issues.apache.org/jira/browse/MAPREDUCE-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena resolved MAPREDUCE-7389. - Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed > Typo

[jira] [Resolved] (MAPREDUCE-7387) Fix TestJHSSecurity#testDelegationToken AssertionError due to HDFS-16563

[ https://issues.apache.org/jira/browse/MAPREDUCE-7387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena resolved MAPREDUCE-7387. - Fix Version/s: 3.4.0 3.3.4 Hadoop Flags: Reviewed

Re: [VOTE] Release Apache Hadoop 2.10.2 - RC0

the help, Ayush. >> >> I committed HADOOP-16663/HADOOP-16664 and cherry-picked HADOOP-16985 to >> branch-2.10 (and branch-3.2). >> If I need to cut RC1, I will try cherry-picking them to branch-2.10.2 >> >> Masatake Iwasaki >> >> >> On 2022/05/28 5:23

Re: [VOTE] Release Apache Hadoop 2.10.2 - RC0

The checksum stuff was addressed in HADOOP-16985, so that filename stuff is sorted only post 3.3.x BTW it is a known issue: https://issues.apache.org/jira/browse/HADOOP-16494?focusedCommentId=16927236&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16927236 Must not

Re: [VOTE] Release Apache Hadoop 3.3.3 (RC1)

+1, * Built from source. * Successful native build on Ubuntu 18.04 * Verified Checksums. (CHANGELOG.md,RELEASENOTES.md,hadoop-3.3.3-rat.txt,hadoop-3.3.3-site.tar.gz,hadoop-3.3.3-src.tar.gz,hadoop-3.3.3.tar.gz) * Verified Signature. * Successful RAT check * Ran basic HDFS shell commands. * Ran basic

[jira] [Resolved] (MAPREDUCE-7376) AggregateWordCount fetches wrong results

[ https://issues.apache.org/jira/browse/MAPREDUCE-7376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena resolved MAPREDUCE-7376. - Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed

Re: [VOTE] Release Apache Hadoop 3.3.3

che/hadoop > and Spark build will be able to pick them up for testing. However in > this case I don't see any 3.3.3 jars in the URL. > >> On Fri, May 6, 2022 at 6:24 PM Ayush Saxena wrote: >> >> There were two 3.3.3 staged. The earlier one was with skipShade, the

Re: [VOTE] Release Apache Hadoop 3.3.3

There were two 3.3.3 staged. The earlier one was with skipShade, the date was also april 22, I archived that. Chao can you use the one that Steve mentioned in the mail? On Sat, 7 May 2022 at 06:18, Chao Sun wrote: > Seems there are some issues with the shaded client as I was not able > to compil

Re: [VOTE] Release Apache Hadoop 3.3.3

+1, * Built from source * Successful native build on Ubuntu 18.04 * Verified Checksums (CHANGELOG.md,RELEASENOTES.md,hadoop-3.3.3-rat.txt,hadoop-3.3.3-site.tar.gz,hadoop-3.3.3-src.tar.gz,hadoop-3.3.3.tar.gz) * Successful RAT check * Ran some basic HDFS shell commands * Ran some basic YARN shell com

Re: Aggregate Word Count from the Mapreduce examples

ing, apart from the fact that the Aggregate WordCount example > uses the Aggregate framework of Hadoop? - as mentioned here in > https://stackoverflow.com/questions/24105117/how-to-execute-aggreagatewordcount-example-in-hadoop-which-uses-hadoop-aggregate#comment37203837_24105117 > >

[jira] [Created] (MAPREDUCE-7376) AggregateWordCount fetches wrong results

Ayush Saxena created MAPREDUCE-7376: --- Summary: AggregateWordCount fetches wrong results Key: MAPREDUCE-7376 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7376 Project: Hadoop Map/Reduce

Fwd: Applications for Travel Assistance to ApacheCon NA 2022 now open

Forwarded as asked in the mail. -Ayush Begin forwarded message: > From: Gavin McDonald > Date: 4 April 2022 at 1:56:40 PM IST > To: travel-assista...@apache.org > Subject: Applications for Travel Assistance to ApacheCon NA 2022 now open > Reply-To: tac-ap...@apache.org > > Hello, Apache PMCs

Re: [DISCUSS] Race condition in ProtobufRpcEngine2

Hey Andras, I had a quick look at HADOOP-18143, the methods in question in ProtobufRpcEngine2 are identical to the ones in ProtobufRpcEngine. So, I am not very sure how the race condition doesn't happen in ProtobufRpcEngine. I have to debug and spend some more time, considering that I have revert

Re: Possibility of using ci-hadoop.a.o for Nutch integration tests

Moved to Dev lists. Not sure about this though: when a PR is submitted to Nutch project it will run some MR job in Hadoop CI. Whatever that PR requires should run as part of Nutch Infra. Why in Hadoop CI? Our CI is already loaded with our own workloads. If by any chance the above assertion gets

[jira] [Resolved] (MAPREDUCE-7368) DBOutputFormat.DBRecordWriter#write must throw exception when it fails

[ https://issues.apache.org/jira/browse/MAPREDUCE-7368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena resolved MAPREDUCE-7368. - Fix Version/s: 3.4.0 Resolution: Fixed > DBOutputFormat.DBRecordWriter#wr

Re: [DISCUSS] Merging PRs vs. commit from CLI and keep committer field

d, at least last year it did when I tried. :-) > > > Thanks for this dirty hack :) > Probably I will refrain from doing this, I don't like to force push if it's > not "mandatory". > Anyway, if the community is fine with it, I will continue to commit from > th

Re: [DISCUSS] Merging PRs vs. commit from CLI and keep committer field

Yahh, remember chasing Github support regarding this last year and they reverted back that they are aware of this and have an internal jira for this but can not comment upon how much time it would take. (As of now 1 year & counting) As far as I remember this is with squash & commit only. If you

Re: [DISCUSS] Checkin Hadoop code formatter

Thanx Viraj for initiating, Makes sense to me to include a formmater inline with our checkstyle rules in the code, would make life simpler for all devs. -Ayush > On 12-Sep-2021, at 12:28 AM, Viraj Jasani wrote: > > + common-...@hadoop.apache.org > > -- Forwarded message - > F

Re: [DISCUSS] Hadoop 3.3.2 release?

+1, Thanx Chao for volunteering!!! > On 07-Sep-2021, at 10:36 PM, Chao Sun wrote: > > Hi all, > > It has been almost 3 months since the 3.3.1 release and branch-3.3 has > accumulated quite a few commits (118 atm). In particular, Spark community > recently found an issue which prevents one from

Re: Yetus unable to build YARN / HADOOP for any patch

pre commit jobs as well and see if things work. I can check and get the creds stuff sorted out in a couple of days… -Ayush > On 05-Jul-2021, at 6:31 PM, Ayush Saxena wrote: > Yeps, something is broken since last week. I tried a bunch of things on > HDFS-PreCommit this weekend, ke

Re: Yetus unable to build YARN / HADOOP for any patch

Yeps, something is broken since last week. I tried a bunch of things on HDFS-PreCommit this weekend, kept on solving issues one after the other. https://issues.apache.org/jira/browse/HADOOP-17787?focusedCommentId=17374212&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#com

Re: [VOTE] Release Apache Hadoop 3.3.1 RC3

+1, Built from Source. Successful Native Build on Ubuntu 20.04 Verified Checksums Ran basic hdfs shell commands. Ran simple MR jobs. Browsed NN,DN,RM and NM UI. Thanx Wei-Chiu for driving the release. -Ayush > On 12-Jun-2021, at 1:45 AM, epa...@apache.org wrote: > > +1 (binding) > Eric > >

Re: [VOTE] Hadoop 3.1.x EOL

+1 -Ayush > On 03-Jun-2021, at 11:26 PM, hemanth boyina > wrote: > > +1 > > Thanks > HemanthBoyina > >> On Thu, 3 Jun 2021, 20:33 Wanqiang Ji, wrote: >> >> +1 (non-binding) >> >> Wanqiang Ji >> >>> On Thu, Jun 3, 2021 at 10:47 PM Sangjin Lee wrote: >>> >>> +1 >>> >>> On Thu, Jun 3, 2

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

[jira] [Resolved] (MAPREDUCE-7343) Increase the job name max length in mapred job -list

[ https://issues.apache.org/jira/browse/MAPREDUCE-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena resolved MAPREDUCE-7343. - Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Assignee: Ayush Saxena

Re: [DISCUSS] check style changes

If you tend to change the line limit, It should have a proper DISCUSS and VOTE thread. If I remember it correct for ozone it was discussed to increase the limit to 100 from 80 and that got vetoed. So, we too should get an agreement first. Well I have gone through the ozone discussion and I also

[jira] [Created] (MAPREDUCE-7343) Increase the job name max length in mapred job -list

Ayush Saxena created MAPREDUCE-7343: --- Summary: Increase the job name max length in mapred job -list Key: MAPREDUCE-7343 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7343 Project: Hadoop Map

Re: [DISCUSS] hadoop-thirdparty 1.1.0 release

b/Hadoop-trunk-Commit/ after every > commit. > However, we don't seem to publish hadoop-thirdparty regularly. (Apache nexus: > https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/thirdparty/) > > Are they published manually? > > >>

Re: [DISCUSS] hadoop-thirdparty 1.1.0 release

Regarding Guava: before release once you merge the change to thrirdparty repo, can update the hadoop thirdparty snapshot, the hadoop code would pick that up, and watch out everything is safe and clean before release. Unless you have a better way to verify or already verified!!! -Ayush > On 23

Re: [DISCUSS] Hadoop 3.3.1 release

+1 Just to mention we would need to release hadoop-thirdparty too before. Presently we are using the snapshot version of it. -Ayush > On 28-Jan-2021, at 6:59 AM, Wei-Chiu Chuang wrote: > > Hi all, > > Hadoop 3.3.0 was released half a year ago, and as of now we've accumulated > more than 400

Re: Intervention. Stabilizing Yetus (Attn. Azure)

The failing Azure tests are being tracked at HADOOP-17325 https://issues.apache.org/jira/browse/HADOOP-17325 On Mon, 9 Nov 2020 at 23:02, Ahmed Hussein wrote: > I created new Jiras for HDFS failures. Please consider doing the same for > Yarn and Azure. > For convenience, the list of failures in

Re: Precommit job fails to write comments in the GitHub pull requests

Hi Akira, Thanx for working on this. Is there anything blocking here? I think it isn’t working still. Can we point to a commit before Yetus-994 instead of master and get away with this? or if there is no solution handy we may go ahead with approach #4 and then figure out how to proceed. -Ayush

Re: [VOTE] Moving Ozone to a separated Apache project

+1 -Ayush > On 25-Sep-2020, at 11:30 AM, Elek, Marton wrote: > > Hi all, > > Thank you for all the feedback and requests, > > As we discussed in the previous thread(s) [1], Ozone is proposed to be a > separated Apache Top Level Project (TLP) > > The proposal with all the details, motivatio

Re: [VOTE] Apache Hadoop Ozone 1.0.0 RC1

+1 * Built from source * Verified checksums & signature * Ran some basic shell commands. Thanx Sammi for driving the release. Good Luck!!! -Ayush On Tue, 1 Sep 2020 at 13:20, Mukul Kumar Singh wrote: > Thanks for preparing the RC Sammi. > > +1 (binding) > > 1. Verified Signatures > > 2. Compil

Re: [DISCUSS] fate of branch-2.9

+1 -Ayush > On 27-Aug-2020, at 6:24 PM, Steve Loughran > wrote: > >  > > +1 > > are there any Hadoop branch-2 releases planned, ever? If so I'll need to > backport my s3a directory compatibility patch to whatever is still live. > > >> On Thu, 27 Aug 2020 at 06:55, Wei-Chiu Chuang wrote:

Re: [RESULT][VOTE] Rlease Apache Hadoop-3.3.0

the first > > release > > > to support the ARM in hadoop. > > > > > > > > > Binding +1s > > > > > > = > > > Akira Ajisaka > > > Vinayakumar B > > > Inigo Goiri > > > Surendra Singh Lilhore >

Re: [VOTE] Release Apache Hadoop 3.3.0 - RC0

+1(non-binding) * Built from source on Ubuntu-18.04 (ARM & x86) * Successful native build. * Ran some basic HDFS shell commands. * Browsed through the WebUI (NN, DN, RM & NM) * Executed WordCount, TeraGen, TeraSort & TeraValidate * Verified checksums and signatures. Thanx everyone for the efforts

Re: [VOTE] Release Apache Hadoop 3.1.4 (RC1)

Hi Gabor, As you are going ahead with another RC, Please include : HDFS-15323 as well if possible. https://issues.apache.org/jira/browse/HDFS-15323 Remember tagging you there but at that time RC0 was up, try if that could make into the release as well. Thanx!!! -Ayush On Wed, 24 Jun 2020 at 16:

Re: [DISCUSS] Hadoop 3.3.0 Release include ARM binary

YARN-10314 also seems to be a blocker. https://issues.apache.org/jira/browse/YARN-10314 We should wait for that as well, should get concluded in a day or two. -Ayush > On 15-Jun-2020, at 7:21 AM, Sheng Liu wrote: > > The HADOOP-17046 has

Re: [ANNOUNCE] New Apache Hadoop Committer - He Xiaoqiao

Congratulations He Xiaoqiao!!! -Ayush > On 11-Jun-2020, at 9:30 PM, Wei-Chiu Chuang wrote: > > In bcc: general@ > > It's my pleasure to announce that He Xiaoqiao has been elected as a > committer on the Apache Hadoop project recognizing his continued > contributions to the > project. > > Ple

  1   2   >