Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

+1 (non-binding) Thanks, Sangjin On Fri, May 24, 2013 at 8:48 PM, Konstantin Boudnik wrote: > All, > > I have created a release candidate (rc0) for hadoop-2.0.4.1-alpha that I > would > like to release. > > This is a stabilization release that includes fixed for a couple a of > issues > discov

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

+1 (non-binding) Thanks Cos. Sangjin On Fri, May 31, 2013 at 4:04 PM, Konstantin Boudnik wrote: > All, > > I have created a release candidate (rc0) for hadoop-2.0.5-alpha that I > would > like to release. > > This is a stabilization release that includes fixed for a couple a of > issues > dis

Re: [ANNOUNCE] New Hadoop PMC members

Congratulations! On Mon, Jun 10, 2013 at 5:00 PM, wrote: > Congratulations guys! > > Steven Y > > > Quoting "Aaron T. Myers" : > > Welcome aboard, folks! >> >> Best, >> Aaron >> >> >> On Mon, Jun 10, 2013 at 8:38 AM, Tom White wrote: >> >> On behalf of the Apache Hadoop PMC, I'm pleased to a

issues.apache.org down?

Is it just me or is issues.apache.org down? From my network, traceroute is unable to get to issues.apache.org. What is the way to report issues with issues.apache.org (no pun)? Thanks, Sangjin

Re: issues.apache.org down?

OK thanks. Sangjin On Tue, Jun 11, 2013 at 11:07 AM, Ted Yu wrote: > I experience the same problem. > > I think infrastruct...@apache.org should be notified. > > Cheers > > On Tue, Jun 11, 2013 at 11:05 AM, Sangjin Lee wrote: > > > Is it just me or is issues.ap

Re: issues.apache.org down?

Tue, Jun 11, 2013 at 11:19 AM, Jean-Daniel Cryans >wrote: > > > https://twitter.com/infrabot/status/344503826457432065 > > > > On Tue, Jun 11, 2013 at 11:14 AM, Sangjin Lee wrote: > > > OK thanks. > > > > > > Sangjin > > > > &g

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

+1 (binding). It's long overdue IMHO. On Thu, May 20, 2021 at 2:11 PM Gergely Pollak wrote: > I really like this initiative, thank you! > +1 for line length increase to 100 characters. > > Regards, > Gergely Pollak > > On Thu, May 20, 2021 at 8:30 PM Vivek Ratnavel > wrote: > > > +1 (non-bind

Re: [VOTE] Hadoop 3.1.x EOL

+1 On Thu, Jun 3, 2021 at 7:35 AM Sean Busbey wrote: > +1 > > > On Jun 3, 2021, at 1:14 AM, Akira Ajisaka wrote: > > > > Dear Hadoop developers, > > > > Given the feedback from the discussion thread [1], I'd like to start > > an official vote > > thread for the community to vote and start the 3

Re: [DISCUSS] IPV6 Support for Hadoop

+1 in understanding where this effort is and what it would take to get this done. I haven't been intimately involved in Hadoop lately, so I can't speak to the level of effort. But I can comment on the importance of Hadoop supporting IPv6 from the customer perspective. What is the complexity or dif

Re: building branch-2 on windows

How do other branches fare in that regard (I don't have easy access to a windows machine atm)? On Fri, Oct 30, 2015 at 7:20 AM, Steve Loughran wrote: > > On 28 Oct 2015, at 21:28, Chris Nauroth cnaur...@hortonworks.com>> wrote: > > I just confirmed that I can build the release-2.6.2-RC0 tag fro

continuing releases on Apache Hadoop 2.6.x

As you may have seen, 2.6.2 is out . I have also retargeted all open issues that were targeted for 2.6.2 to 2.6.3. Continuing the discussion in the email thread here , I'd like us to maintain the cadence of m

Re: Need for force-push on feature branches

I already opened an INFRA JIRA for my specific issue (INFRA-10745 ), and also sent email to them. Steve Loughran made me aware of the lockdown there. We can reuse that JIRA for this discussion? I don't mind following up later, as we're blocked (YA

Re: Need for force-push on feature branches

If we do use "feature/..." as the branch naming convention, it does pose an issue with the patch naming due to the separator character ('/'). How about "feature-..."? On Tue, Nov 10, 2015 at 3:02 PM, Anu Engineer wrote: > I ran into the same issue and filed an INFRA jira too. > > https://issues

Re: [DISCUSS] Looking to a 2.8.0 release

On Wed, Nov 11, 2015 at 12:13 PM, Vinod Vavilapalli wrote: > — YARN Timeline Service Next generation: YARN-2928: Lots of momentum, > but clearly a work in progress. Two options here > — If it is safe to ship it into 2.8 in a disable manner, we can > get the early code into trunk and a

Re: Need for force-push on feature branches

M, Steve Loughran wrote: > > > On 11 Nov 2015, at 22:47, Sangjin Lee wrote: > > > > If we do use "feature/..." as the branch naming convention, it does pose > an > > issue with the patch naming due to the separator character ('/'). How > about

Re: Need for force-push on feature branches

Nov 2015, at 17:49, Sangjin Lee wrote: > > > > Yes, I completely understand about the git branch naming practice (in > fact > > that's what I normally do). I was commenting on our hadoop patch naming > > convention. We are supposed to use patch names as > > &qu

Re: Need for force-push on feature branches

atch identification rules are definitely > ‘not trivial’. > > FWIW, the documented ruleset Yetus supports is here: > > > https://yetus.apache.org/documentation/latest/precommit-patchnames/ > > (Altho, in reality, the code does support more than this but they are sort > of w

Re: [DISCUSS] Looking to a 2.8.0 release

oks rather challenging given the suggested timeframe. We also need to complete several major tasks before it is ready. Sangjin On Wed, Nov 11, 2015 at 5:49 PM, Sangjin Lee wrote: > > On Wed, Nov 11, 2015 at 12:13 PM, Vinod Vavilapalli < > vino...@hortonworks.com> wrote: > &g

Re: continuing releases on Apache Hadoop 2.6.x

do end up backporting patches after that, you > should set the fix-version to be 2.6.1. > > Thanks > +Vinod > > > > On Nov 2, 2015, at 11:29 AM, Sangjin Lee wrote: > > > > As you may have seen, 2.6.2 is out > > <http://markmail.org/thread/yw53xgz6wzpqncl

Re: continuing releases on Apache Hadoop 2.6.x

> > > > In the mean while, we should also review 2.7.3 and 2.8.0 blocker / > > critical list and see if it makes sense to backport any of those into > 2.6.3. > > > > +Vinod > > > > > > On Nov 17, 2015, at 5:10 PM, Sangjin Lee > sj...@apac

Re: continuing releases on Apache Hadoop 2.6.x

less they are > critical enough as blocker. We can nominate more fixes later in 2.6.4. > Thoughts? > > Thanks, > > Junping > > From: sjl...@gmail.com on behalf of Sangjin Lee < > sj...@apache.org> > Sent: Frid

Re: Nightly Jenkins job for maintenance releases

FWIW when I used it during the 2.6.2 release (thanks Andrew for setting this up), the builds never finished completely due to memory issues. Some tuning and debugging would be needed to make this work reliably. Sangjin On Mon, Nov 30, 2015 at 11:18 AM, Andrew Wang wrote: > I set up a parameteri

Re: Update BUILDING.txt instructions for Eclipse

I've used both ways of setting up hadoop for eclipse, and one issue I see with m2eclipse is that it doesn't seem to set up the code-generated protobuf classes properly. As a result, the workspace comes out with tons of errors to begin with. Has anyone solved this issue? Sangjin On Thu, Dec 3, 201

Re: [VOTE] Release Apache Hadoop 2.6.3 RC0

+1 (non-binding) - downloaded source and binary and verified the signatures (although I didn't connect with Junping via web of trust) - started a pseudo-distributed cluster and ran test jobs - browsed the RM and NN UI - looked through the daemon logs Thanks Junping. Sangjin On Wed, Dec 16, 2015

setting up a local ubuntu VM for building and testing hadoop

Has anyone set up an ubuntu VM to build hadoop and run unit tests locally? I'm familiar with setting up a linux machine to build and test hadoop, but a VM (I'm using Parallels on mac) seems to cause issues regarding resolving the localhost address. I get all kinds of UnknownHostExceptions and varia

Re: setting up a local ubuntu VM for building and testing hadoop

M, Arun Suresh wrote: > Hello Sangjin > I had similar problems recently.. Got around it by modifying my /etc/hosts. > I just update the 127.0.0.1 entry to add the short hostname of the machine > like so : > ... > 127.0.0.1 localhost > ... > > > On Wed, Jan 6, 2016 at 8

Re: Need for force-push on feature branches

reach out to > INFRA again? > > On Thu, Nov 12, 2015 at 10:21 AM, Allen Wittenauer > wrote: > > > > > > > > > > > > On Nov 12, 2015, at 10:14 AM, Sangjin Lee wrote: > > > > > > I don't think we're proposing project-specific rules. It wo

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

I agree that it would be a good practice to maintain parity between 2.6.x and 2.7.x as much as possible. Departure from it should be more of an exception than the norm. That said, it is also true that we're not exactly following the semantic versioning the moment we started to maintain multiple si

Re: [UPDATE] New ASF git policy on force-pushes / Tags / Stale branches

Thanks Vinod for the proposal. I deleted my branch (sjlee/hdfs-merge) the other day. Sangjin On Thu, Jan 14, 2016 at 1:26 PM, Vinod Kumar Vavilapalli wrote: > Hi all, > > As some of you have noticed, we have an update from ASF infra on git > branching policy: We no longer have a ASF wide mandat

Re: [UPDATE] New ASF git policy on force-pushes / Tags / Stale branches

ture-YARN-2928 to YARN-2928 to follow our practice for branch > development. Thoughts? > > > Thanks, > > Junping > ________ > From: sjl...@gmail.com on behalf of Sangjin Lee < > sj...@apache.org> > Sent: Friday, January 15, 2016

Re: [VOTE] Release Apache Hadoop 2.6.4 RC0

+1 (not binding) - downloaded both the source and the binary tarballs, and checked the checksums and signatures - started a pseudo-distributed cluster and ran test MR jobs - spot checked the URI and the logs Sangjin On Mon, Feb 8, 2016 at 4:17 PM, Jason Lowe wrote: > +1 (binding) > - verified

Re: Looking to a Hadoop 3 release

Another thing to throw in there is the dependency/classpath isolation (HADOOP-11656). Some efforts have already been made by Sean, and it'd be great to complete this to have a much better dependency isolation solution for 3.x. On Thu, Feb 18, 2016 at 5:33 PM, Gangumalla, Uma wrote: > Yes. I thin

Re: [Release thread] 2.8.0 release activities

Where do we stand in terms of closing out blocker/critical issues for 2.8.0? I still see 50 open JIRAs in Vinod's list: https://issues.apache.org/jira/issues/?filter=12334985 But I see a lot of JIRAs with no patches or very stale patches. It would be a good exercise to come up with the list of JIR

Re: [Release thread] 2.8.0 release activities

elp with reviewing Common/HDFS > JIRAs. > > Thanks, > Wangda > > > On Wed, May 11, 2016 at 4:20 PM, Sangjin Lee wrote: > > > Where do we stand in terms of closing out blocker/critical issues for > > 2.8.0? I still see 50 open JIRAs in Vinod's list: > > http

Re: [Release thread] 2.8.0 release activities

gda > > > On Wed, May 11, 2016 at 5:06 PM, Sangjin Lee wrote: > >> How about this? I'll review the HADOOP/HDFS bugs in that list to come up >> with true blockers for 2.8.0 or JIRAs that are close to being ready. I'll >> report the list here. Then folks ca

Re: Compatibility guidelines for toString overrides

+1. Thanks, Sangjin On Thu, May 12, 2016 at 10:05 AM, Ravi Prakash wrote: > Thanks sounds reasonable Colin. +1 to not using toString() as an API > > On Thu, May 12, 2016 at 9:57 AM, Chris Nauroth > wrote: > > > I'm in favor of making a statement in the compatibility guidelines that > > there i

Re: Different JIRA permissions for HADOOP and HDFS

I also find myself unable to edit most of the JIRA fields, and that is across projects (HADOOP, YARN, MAPREDUCE, and HDFS). Commenting and the workflow buttons seem to work, however. On Mon, May 16, 2016 at 8:14 AM, Zhihai Xu wrote: > Great, Thanks Junping! Yes, the JIRA assignment works for me

Re: Different JIRA permissions for HADOOP and HDFS

t; just add you into committer roles for 4 projects. Hope it works for > you now.​ > > > Thanks, > > > Junping > -- > *From:* sjl...@gmail.com on behalf of Sangjin Lee < > sj...@apache.org> > *Sent:* Monday, May 16, 2016 11:43 PM &g

Re: Hadoop branch-2 build is broken

No, I think it is this commit: https://github.com/apache/hadoop/commit/e205421555841dbf482d6aa1464cc15788b2b1fb (HADOOP-13157). On Tue, May 17, 2016 at 6:13 PM, Xiaoyu Yao wrote: > Hadoop Branch-2 build is broken by this commit. > > ac8fb579c6058fec60caf30682f902413d68edf3: "Remove parent's env

Re: [DISCUSS] Replacing the automatic Jenkins jobs with Apache Yetus qbt

Sounds good. +1. On Thu, Jun 2, 2016 at 3:28 AM Steve Loughran wrote: > > > On 1 Jun 2016, at 04:53, Andrew Wang wrote: > > > > I'm in favor of something that helps unify the current mess of Jenkins > > jobs. We do something similar for our internal Hadoop repo: each branch > has > > a "build.sh

Re: [DISCUSS] Increased use of feature branches

Having worked on a major feature in a feature branch, I have some thoughts and observations on feature branch development. IMO feature branch development v. direct commits to trunk in piecemeal is really a choice of *granularity*. Do we want a series of fine-grained state changes on trunk or fewer

Re: [DISCUSS] Increased use of feature branches

a 3-day voting period > instead of 7, or treat it just like today’s commit to trunk – but with 2 > people signing-off? > > What I am suggesting is reducing the administrative overheads of using a > branch to encourage use of branching. > Right now it feels like Apache’s process en

feature branch merge policy

Hi folks, Is there a standard policy for merging a feature branch onto trunk? I'm specifically looking for answers for - How is the commit done? Squash commit? Patch? Something else? - What should the commit message contain? - Do we preserve the feature branch after the commit for the commit histo

Re: feature branch merge policy

gt; https://lists.apache.org/thread.html/43cd65c6b6c3c0e8ac2b3c76afd9eff1f78b177fabe9c4a96d9b3d0b@1440189889@%3Ccommon-dev.hadoop.apache.org%3E > > I never got around to adding this text to the website though, TODO. > > Best, > Andrew > > On Thu, Jun 16, 2016 at 2:09 PM, Sangjin Lee

hadoop-lzo 0.4.17 released

This is a somewhat belated notice, but I thought I'd mention that we released hadoop-lzo 0.4.17 a couple of weeks ago: https://github.com/twitter/hadoop-lzo One of the main changes that went into 0.4.17 is to make it compatible with hadoop 2.0.x. Thanks, Sangjin

Re: Java 7 and Hadoop

This is how we work through this in hadoop-lzo using profiles: https://github.com/twitter/hadoop-lzo/blob/master/pom.xml#L105 Of course, if we have more than one use for profiles things would get hairy quickly. FWIW. Sangjin On Sat, Aug 3, 2013 at 1:34 AM, Steve Loughran wrote: > would be nice

issues with distcp copying from 1.0 to 2.0

This may have been discussed in the past, but I haven't been able to find one... It seems as though much work has been done to make distcp from 1.0 to 2.0 work with checksum enabled ( https://issues.apache.org/jira/browse/HADOOP-8060). And I do see all the work has been merged to the 2.0 releases.

branch development for HADOOP-9639

We have been having discussions on HADOOP-9639 (shared cache for jars) and the proposed design there for some time now. We are going to start work on this and have it vetted and reviewed by the community. I have just filed some more implementation JIRAs for this feature: YARN-1465, MAPREDUCE-5662,

Re: Logistics for releasing 2.4

I also wanted to bring your attention to HADOOP-9652. As this would address a major performance issue with the local filesystem, it would be good to get this in for 2.4 (or is it 2.3?). Regards, Sangjin On Thu, Jan 23, 2014 at 2:23 AM, Steve Loughran wrote: > the JIRA I referenced is ready to g

Re: [VOTE] Release Apache Hadoop 2.3.0

If it's not too late, I'd like to bring your attention to YARN-1692. We get a ConcurrentModificationException with the fair scheduler when it updates demand, and we saw RM get into a pretty bad shape around the time this happened. It would be great if this could make 2.3.0. I provided a patch for

very old dependencies

Hi folks, Even as 2.3 was released, several dependencies of hadoop are quite dated. And more and more of them are causing friction for hadoop-related libraries and hadoop users in general, as these dependency versions are often incompatibly different than the versions most people use these days. S

Re: very old dependencies

ging them could break jobs that rely on them. For jobs > that want to use newer versions, the recommendation is to use > mapreduce.user.classpath.first or turn on classpath isolation with > mapreduce.job.classloader. > > -Sandy > > > On Fri, Mar 28, 2014 at 7:59 AM, Sangjin Le

Re: very old dependencies

I agree. We should still be diligent in keeping dependencies up-to-date as long as the changes are fairly non-destructive (I hear you about guava). That would be a pretty big service to not only users but also developers of libraries on hadoop. On Fri, Mar 28, 2014 at 11:04 AM, Steve Loughran wr

Re: Plans of moving towards JDK7 in trunk

Please don't forget the mac os build on JDK 7. :) On Fri, Apr 4, 2014 at 3:15 PM, Haohui Mai wrote: > I'm referring to the later case. Indeed migrating JDK7 for branch-2 is more > difficult. > > I think one reasonable approach is to put the hdfs / yarn clients into > separate jars. The client-s

Re: Plans of moving towards JDK7 in trunk

I would say, to an extent. The current state of the jetty version is *severe*. We're 3 major versions behind, and if my understanding is correct, it was a long time ago they EOF'ed version 6.x. Yes, upgrading jetty could break some customers. However, we need to view it in balance. We're constantl

Re: hadoop-2.5 - June end?

It would be great if we can consider the shared cache (YARN-1492) as part of 2.5. It obviously will depend on the reviews from folks, but the feature itself should be reasonably solid. Thanks, Sangjin On Mon, Jun 23, 2014 at 2:24 PM, Arun C Murthy wrote: > Thanks Karthik! > > I've updated http

Re: hadoop-2.5 - June end?

, Vinod Kumar Vavilapalli < > >> > vino...@apache.org > >> > > wrote: > >> > > >> > > I started reviewing YARN-1492 and synced up offline with Sangjin and > >> > Chris > >> > > who are leading this. I proposed that we shoul

Re: [VOTE] Migration from subversion to git for version control

+1 (non-binding) On Sat, Aug 9, 2014 at 9:34 AM, Sandy Ryza wrote: > +1 (binding) > > > On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla > wrote: > > > I have put together this proposal based on recent discussion on this > topic. > > > > Please vote on the proposal. The vote runs for 7 days. >

Re: Git repo ready to use

It seems like the github mirror at https://github.com/apache/hadoop-common has stopped getting updates as of 8/22. Could this mirror have been broken by the git transition? Thanks, Sangjin On Fri, Aug 29, 2014 at 11:51 AM, Ted Yu wrote: > From https://builds.apache.org/job/Hadoop-hdfs-trunk/18

Re: Git repo ready to use

That's good to know. Thanks. On Wed, Sep 3, 2014 at 11:15 PM, Vinayakumar B wrote: > I think its still pointing to old svn repository which is just read only > now. > > You can use latest mirror: > https://github.com/apache/hadoop > > Regards, > Vinay > On Se

Re: Time to address the Guava version problem

I would also agree on upgrading guava. Yes I am aware of the potential impact on customers who might rely on hadoop bringing in guava 11. However, IMHO the balance tipped over to the other side a while ago; i.e. I think there are far more people using guava 16 in their code and scrambling to make t

Re: Time to address the Guava version problem

lso > break user applications, but it might be the driving feature for Hadoop > 3.0? > > On Fri, Sep 19, 2014 at 5:13 PM, Sangjin Lee wrote: > > > I would also agree on upgrading guava. Yes I am aware of the potential > > impact on customers who might rely on hadoop brin

Re: Thinking ahead to hadoop-2.6

I am also +1 for the end of next week. YARN-1492 (shared cache) is near the final stages of the review, and with a little more time it would make it easier to put it in. On Tue, Sep 23, 2014 at 4:48 PM, Subramaniam V K wrote: > +1 for end of next week. > > We have got all the patches for YARN-10

Re: What's the difference between branch-3 and branch-3.0?

+1 on deleting branch-3. On Wed, Jan 17, 2018 at 10:42 AM, Jason Lowe wrote: > This was created accidentally when HDFS-11847 was committed. As such we > should delete the branch-3 branch and port over the commits that went into > branch-3 instead of branch-3.0. For the former, I'm assuming tha

Re: HADOOP-14163 proposal for new hadoop.apache.org

+1. Thanks for the work, Marton! On Fri, Aug 31, 2018 at 8:37 AM Vinod Kumar Vavilapalli wrote: > Is there no way to host the new site and the old site concurrently? And > link back & forth? > > +Vinod > > > > On Aug 31, 2018, at 1:07 AM, Elek, Marton wrote: > > > > Bumping this thread at last

Re: [VOTE] Force "squash and merge" option for PR merge on github UI

+1. Sounds good to me. On Wed, Jul 17, 2019 at 10:20 AM Iñigo Goiri wrote: > +1 > > On Wed, Jul 17, 2019 at 4:17 AM Steve Loughran > > wrote: > > > +1 for squash and merge, with whoever does the merge adding the full > commit > > message for the logs, with JIRA, contributor(s) etc > > > > One l

Re: [DISCUSS] Removing the archiac master branch

+1 On Fri, Jun 19, 2020 at 11:27 AM Eric Badger wrote: > +1 > > Eric > > On Fri, Jun 19, 2020 at 1:14 PM Ayush Saxena wrote: > > > Thanx Owen for initiating. > > +1 > > -Ayush > > > > > On 19-Jun-2020, at 10:52 PM, Zhe Zhang wrote: > > > > > > +1 Thanks Owen > > > > > > I scratched my head fo

Re: [DICUSS] Upgrading Guice to 4.0(HADOOP-12064)

Yeah it would be awesome if we can get feedback and/or suggestions on these JIRAs (HADOOP-11804 and HADOOP-13070). Thanks, Sangjin On Wed, Jun 29, 2016 at 10:55 AM, Sean Busbey wrote: > At the very least, I'm running through an updated shaded hadoop client > this week[1] (HBase is my test appli

Re: Feedback on IRC channel

I seldom check out IRC (as my experience was the same). I'm OK with retiring it if no committers are around. On a related note, I know Tsuyoshi set up a slack channel for the committers. Even that one is pretty idle. :) Should we use it more often? If that starts to gain traction, we could set up

[DISCUSS] 2.6.x line releases

It's been a while since we had a release on the 2.6.x line. Is it time to get ready for a 2.6.5 release? Are folks using and relying on releases on 2.6.x? If there is enough interest, I could take that on. Let me know. I also want to gauge the community's interest in maintaining the 2.6.x line. Ho

Re: [DISCUSS] The order of classpath isolation work and updating/shading dependencies on trunk

Thanks Tsuyoshi for opening the discussion. One benefit of the dependency/classpath isolation work is that it can open up a possibility of having diverging dependencies in a safe manner so that upgrading libraries may have less impact. I'll spend some more time on HADOOP-13070 to make some progress

Re: [DISCUSS] 2.6.x line releases

LTS. > > Ubuntu Server LTS is maintained for 5 years but the other releases are > not. > > > > Regards, > > Akira > > > > On 7/20/16 12:45, Sean Busbey wrote: > > > >> The HBase community would like more 2.6.z releases. > >> > >>

Re: [DISCUSS] The order of classpath isolation work and updating/shading dependencies on trunk

The work on HADOOP-13070 and the ApplicationClassLoader are generic and go beyond YARN. It can be used in any JVM that uses hadoop. The current use cases are MR containers, hadoop's RunJar (as in "hadoop jar"), and the YARN node manager auxiliary services. I'm not sure if that's what you were askin

Re: Setting JIRA fix versions for 3.0.0 releases

On Thu, Jul 21, 2016 at 3:58 PM, Andrew Wang wrote: > Thanks for the input Vinod, inline: > > > > Similarly the list of features we are enabling in this alpha would be > good > > - may be update the Roadmap wiki. Things like classpath-isolation which > > were part of the original 3.x roadmap are

Re: [DISCUSS] 2.6.x line releases

Thanks Zhe! On Fri, Jul 22, 2016 at 4:01 PM, Zhe Zhang wrote: > Thanks for pointing it out Allen. I'll work on an addendum 2.6 patch for > HADOOP-12800. > > On Fri, Jul 22, 2016 at 3:59 PM Allen Wittenauer > > wrote: > > > > > > On Jul 22, 2016, at 9:07 AM, Zhe Zhang > > wrote: > > > > > > Tha

Re: [DISCUSS] The order of classpath isolation work and updating/shading dependencies on trunk

oesn't really have an impact on that. > > > On Jul 22, 2016, at 9:57 AM, Sangjin Lee wrote: > > > > The work on HADOOP-13070 and the ApplicationClassLoader are generic and > go beyond YARN. It can be used in any JVM that uses hadoop. The current use > cases are MR

Re: [VOTE] Release Apache Hadoop 2.7.3 RC0

+1 (binding) - downloaded both source and binary tarballs and verified the signatures - set up a pseudo-distributed cluster - ran some simple mapreduce jobs - checked the basic web UI Sangjin On Wed, Jul 27, 2016 at 12:57 PM, John Zhuge wrote: > +1 (non-binding) > > - Build source with Java 1.

HADOOP-13410

I'd like to get feedback from the community (especially those who might remember this) on HADOOP-13410: https://issues.apache.org/jira/browse/HADOOP-13410 It appears that Hadoop's RunJar adds the original jar to the app's classpath even though the unjarred contents of the jar are in the classpath.

Re: HADOOP-13410

n Tue, Aug 9, 2016 at 11:00 AM, Sangjin Lee wrote: > > I'd like to get feedback from the community (especially those who might > > remember this) on HADOOP-13410: > > https://issues.apache.org/jira/browse/HADOOP-13410 > > > > It appears that Hadoop's RunJar

Re: HADOOP-13410

I just tested a simple service loader with the patch and it works fine even if the jar is not in the classpath. On Tue, Aug 9, 2016 at 10:41 AM, Sangjin Lee wrote: > It uses ClassLoader.getResources() so there shouldn't be anything specific > to the form of the resource (jar or not

Re: [Release thread] 2.6.5 release activities

Thanks folks for opening up the discussion on our EOL policy. That's also exactly what I wanted to discuss when I opened up the 2.6.5 discussion: I also want to gauge the community's interest in maintaining the 2.6.x > line. How long do we maintain this line? What would be a sensible EOL > policy?

Re: [DISCUSS] Release cadence and EOL

Thanks Karthik for opening a long overdue discussion on the release cadence and EOL. As for the EOL, I think we need to weigh between the benefit for the users and the maintenance cost for the community. I'd also love to find out what other (major) open source projects do in terms of the EOL. Her

Re: [Release thread] 2.6.5 release activities

Thanks Chris! I'll help Chris to get those JIRAs marked in his spreadsheet committed. We'll cut the release branch shortly after that. If you have any critical change that should be made part of 2.6.5 (CVE patches included), please reach out to us and commit the changes. If all things go well, we'

Re: [Release thread] 2.6.5 release activities

We ported 16 issues to branch-2.6. We will go ahead and start the release process, including cutting the release branch. If you have any critical change that should be made part of 2.6.5, please reach out to us and commit the changes. Thanks! Sangjin On Mon, Sep 12, 2016 at 3:24 PM, Sangjin Lee

[VOTE] Release Apache Hadoop 2.6.5 (RC0)

Hi folks, I have created a release candidate RC0 for the Apache Hadoop 2.6.5 release (the next maintenance release in the 2.6.x release line). Below are the details of this release candidate: The RC is available for validation at: http://home.apache.org/~sjlee/hadoop-2.6.5-RC0/. The RC tag in gi

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC0)

; > > > > The steps I've done: > > > > > > * Downloaded release tar and source tar, verified MD5. > > > * Run a HDFS cluster, and copy files between local filesystem and HDFS. > > > > > > > > > On Tue, Sep 27, 2016 at 1:28 PM, San

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC0)

P-13290 > > ,HDFS-10544, > > HADOOP-13255 > > ,HADOOP-13189 > > > > > --Brahma Reddy Battula > > > -- > *From:* sjl...@gmail.com on behalf of Sangjin Lee < > sj...@apache.org> > *Sent:* Wednesday, September 28, 2016 1:58 AM > *To:* common-dev@hado

Re: Maven build: YARN timeline service downloading maven-metadata from personal repository?

We should raise a JIRA. I suspect this is more of an hbase issue. I believe it's coming from the hbase pom that contains a definition of that repo (named "ghelmling.testing"). This would entail upgrading to a later version of hbase that removes this repo. I don't think this is a major issue, but it

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC0)

et me know what you all think (whether this is something that should stop the RC). Regards, Sangjin On Sat, Oct 1, 2016 at 12:46 PM, Sangjin Lee wrote: > Thanks John and Brahma for reporting issues with CHANGES.txt. > > IMO, we can move ahead with the current RC0 and address these issues

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC0)

ng entries in CHANGES.txt. > When upgrading to 2.6.5, most of admins look at the change logs and see > what bugs are fixed. Therefore I'm thinking the change logs are important > and they should be fixed. > > Thanks, > Akira > > > On 9/28/16 05:28, Sangjin Lee wrote: &g

[VOTE] Release Apache Hadoop 2.6.5 (RC1)

Hi folks, I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5 release (the next maintenance release in the 2.6.x release line). RC1 contains fixes to CHANGES.txt, and is otherwise identical to RC0. Below are the details of this release candidate: The RC is available for valida

Re: Maven build: YARN timeline service downloading maven-metadata from personal repository?

Thanks Wangda. To answer Steve's question, I don't think maven downloads anything from that location (it's a very old content). It just does a wasted effort by hitting this repo. On Mon, Oct 3, 2016 at 10:25 AM, Wangda Tan wrote: > Filed: https://issues.apache.org/jira/browse/HBASE-16749 > > On

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

I looked into building it on jenkins earlier, but it appears that this jenkins job is busted (at least for 2.6.x): https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/ I don't have access to the job configuration, so I'm unable to fix it atm. That said, I do think Allen has a point. I

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

on the WebUI. > > Maybe file a follow-on JIRA to remove it for the future? > > On Thu, Oct 6, 2016 at 3:09 PM, Sangjin Lee wrote: > > > I looked into building it on jenkins earlier, but it appears that this > > jenkins job is busted (at least for 2.6.x): > >

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

> +1(non-binding) > > * verified signature and md5. > * built with -Pnative on CentOS6 and OpenJDK7. > * built documentation and skimmed the contents. > * built rpms by bigtop and ran smoke-tests of hdfs, yarn and mapreduce on > 3-node cluster. > > Thanks, > Masatake I

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

t; > > > * Downloaded and built from source > > > * Verified md5 checksums and signature > > > * Deployed a pseudo cluster > > > * verified basic HDFS operations and Pi job. > > > * Did a sanity check for RM and NM UI. > > > > > > Than

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

> +1 (binding) > > - Verified signatures and digests > - Built native from source > - Deployed to a single-node cluster and ran some sample jobs > > Jason > > > On Sunday, October 2, 2016 7:13 PM, Sangjin Lee wrote: > > > Hi folks, > > I have pushed a new

Re: [DISCUSS] Release cadence and EOL

Reviving an old thread. I think we had a fairly concrete proposal on the table that we can vote for. The proposal is a minor release on the latest major line every 6 months, and a maintenance release on a minor release (as there may be concurrently maintained minor releases) every 2 months. A min

Re: [DISCUSS] Release cadence and EOL

for ~9 months before moving onto a new minor: > http://stackoverflow.com/questions/35997352/how-to- > determine-end-of-life-for-eclipse-versions > > > > On Fri, Oct 28, 2016 at 10:55 AM, Sangjin Lee wrote: > > > Reviving an old thread. I think we had a fairly concrete pr

Re: Updated 2.8.0-SNAPSHOT artifact

+1. Resetting the 2.8 effort and the branch at this point may be counter-productive. IMO we should focus on resolving the remaining blockers and getting it out the door. I also think that we should seriously consider 2.9 as well, as a fairly large number of changes have accumulated in branch-2 (ove

  1   2   3   >