Fwd: question about branches

2012-02-01 Thread Hwa Zynn
Hi, all, I have a newcomer question. I would like to browse HDFS source code for the 1.0 release, but the Git repository (git://git.apache.org/hadoop-hdfs.git) for Hadoop-HDFS project doesn't have this branch, not even 0.20. I can see a lot more branches from Hadoop-Common project ( git://git.apac

[jira] [Created] (HADOOP-8012) hadoop-daemon.sh and yarn-daemon.sh are trying to mkdir and chow log/pid dirs which can fail

2012-02-01 Thread Roman Shaposhnik (Created) (JIRA)
hadoop-daemon.sh and yarn-daemon.sh are trying to mkdir and chow log/pid dirs which can fail Key: HADOOP-8012 URL: https://issues.apache.org/jira/browse/HADOOP-8012

RE: Debugging 1.0.0 with jdb

2012-02-01 Thread Tim Broberg
Terrific, thanks, Harsh. ...and I'll take a stab at bringing eclipse up today. - Tim. From: Harsh J [ha...@cloudera.com] Sent: Wednesday, February 01, 2012 2:51 AM To: common-dev@hadoop.apache.org Subject: Re: Debugging 1.0.0 with jdb I've not used jd

Re: MPI: Java/JNI help

2012-02-01 Thread Ralph Castain
Thanks Kihwal! This was an excellent suggestion and worked great! Should have the Java bindings out shortly... On Jan 31, 2012, at 4:35 PM, Kihwal Lee wrote: > There might be other tricks you can play with CL, but here is my idea: You > could have the initial jni native lib to become a sort of

[jira] [Resolved] (HADOOP-8011) How to use distcp command betwen 2 cluster that different version

2012-02-01 Thread Brian Bloniarz (Resolved) (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-8011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Bloniarz resolved HADOOP-8011. Resolution: Not A Problem > How to use distcp command betwen 2 cluster that different

Re: Debugging 1.0.0 with jdb

2012-02-01 Thread Harsh J
I've not used jdb since I almost always use Eclipse to do this, but to have ant run javac with debug info on, you'll need to find the relevant elements and add the attribute 'debug="on"' to them, to have the javac produce files with debug info. You can then pick up the generated test jar and run i