Re: Updates on migration to git
On 25 August 2014 23:45, Karthik Kambatla ka...@cloudera.com wrote: Thanks for bringing these points up, Zhijie. By the way, a revised How-to-commit wiki is at: https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to make changes and improve it. looks good so far I suspect we'll evolve it rapidly in use. On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen zs...@hortonworks.com wrote: Do we have any convention about user.name and user.email? For example, we'd like to use @apache.org for the email. May be, we can ask people to use project-specific configs here and use their real name and @apache.org address. Is there any downside to letting people use their global values for these configs? I don't see any Moreover, do we want to use --author=Author Name em...@address.com when committing on behalf of a particular contributor? Fetching the email-address is complicated here. Should we use the contributor's email from JIRA? What if that is not their @apache address? I see aw's point, and as he notes, it just increases work. But if we accept git am (squashed) patches, that comes for free. Maybe we should recommend that as the format for future patches. Some other post-migration thoughts 1. This would be a good time to clean up dead branches ... I promise to tag then delete my old work 2. What's our policy of in-asf-git branch dev? Single committer/few committers: --- Say allen's 9902 work, which was a single committer's project, possibly with many little commits? I think people should be allowed to work on feature branches (naming policy? minor/$JIRA(+text) ?. At merge time we'd squash these down to a single patch -this could be the one reviewed. Large feature dev (par with today's feature branch/feature committer) --- we could retain the current policy of JIRA per commit, or we could allow feature-off-feature dev, where people can work on a JIRA in a branch, which is then merged (squashed) back in to the main feature branch. This'd give more visibility of dev work and still isolate the big feature from individual work. At the end of the feature, it could be merged in directly, without any squashing. we could call these something like feature/$JIRA(+text) to highlight they are big works differentiate from the minor projects. we also need to plan for the promotion of minor - feature, which could be done with something like -1 create new feature branch off trunk -2 merge squashed minor branch into new feature Finally, we've all be very lax about working on that pending patch list. Much work, especially those very minor things, have been neglected. If this git migrate eases committing, it's time to go through the backlist and apply them. -steve -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Build failed in Jenkins: Hadoop-Common-0.23-Build #1053
See https://builds.apache.org/job/Hadoop-Common-0.23-Build/1053/ -- [...truncated 8263 lines...] Running org.apache.hadoop.io.TestBloomMapFile Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.875 sec Running org.apache.hadoop.io.TestObjectWritableProtos Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.329 sec Running org.apache.hadoop.io.TestTextNonUTF8 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec Running org.apache.hadoop.io.nativeio.TestNativeIO Tests run: 9, Failures: 0, Errors: 0, Skipped: 9, Time elapsed: 0.158 sec Running org.apache.hadoop.io.TestSortedMapWritable Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.198 sec Running org.apache.hadoop.io.TestMapFile Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.645 sec Running org.apache.hadoop.io.TestUTF8 Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.448 sec Running org.apache.hadoop.io.TestBoundedByteArrayOutputStream Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.042 sec Running org.apache.hadoop.io.retry.TestRetryProxy Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.207 sec Running org.apache.hadoop.io.retry.TestFailoverProxy Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.198 sec Running org.apache.hadoop.io.TestSetFile Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.999 sec Running org.apache.hadoop.io.serializer.TestWritableSerialization Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.316 sec Running org.apache.hadoop.io.serializer.TestSerializationFactory Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.28 sec Running org.apache.hadoop.io.serializer.avro.TestAvroSerialization Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.539 sec Running org.apache.hadoop.util.TestGenericOptionsParser Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.703 sec Running org.apache.hadoop.util.TestReflectionUtils Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.515 sec Running org.apache.hadoop.util.TestJarFinder Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.76 sec Running org.apache.hadoop.util.TestPureJavaCrc32 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.287 sec Running org.apache.hadoop.util.TestHostsFileReader Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.185 sec Running org.apache.hadoop.util.TestShutdownHookManager Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.143 sec Running org.apache.hadoop.util.TestDiskChecker Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.488 sec Running org.apache.hadoop.util.TestStringUtils Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.139 sec Running org.apache.hadoop.util.TestGenericsUtil Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.261 sec Running org.apache.hadoop.util.TestAsyncDiskService Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.127 sec Running org.apache.hadoop.util.TestProtoUtil Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.079 sec Running org.apache.hadoop.util.TestDataChecksum Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.186 sec Running org.apache.hadoop.util.TestRunJar Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.13 sec Running org.apache.hadoop.util.TestOptions Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.084 sec Running org.apache.hadoop.util.TestShell Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.196 sec Running org.apache.hadoop.util.TestIndexedSort Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.599 sec Running org.apache.hadoop.util.TestStringInterner Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.115 sec Running org.apache.hadoop.record.TestRecordVersioning Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.141 sec Running org.apache.hadoop.record.TestBuffer Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.055 sec Running org.apache.hadoop.record.TestRecordIO Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.16 sec Running org.apache.hadoop.security.TestGroupFallback Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.432 sec Running org.apache.hadoop.security.TestGroupsCaching Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.294 sec Running org.apache.hadoop.security.TestProxyUserFromEnv Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.363 sec Running org.apache.hadoop.security.TestUserGroupInformation Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.673 sec Running org.apache.hadoop.security.TestJNIGroupsMapping Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.141 sec Running
[jira] [Created] (HADOOP-11003) org.apache.hadoop.util.Shell should not take a dependency on binaries being deployed when used as a library
Remus Rusanu created HADOOP-11003:
-
Summary: org.apache.hadoop.util.Shell should not take a dependency
on binaries being deployed when used as a library
Key: HADOOP-11003
URL: https://issues.apache.org/jira/browse/HADOOP-11003
Project: Hadoop Common
Issue Type: Bug
Components: util
Environment: Windows
Reporter: Remus Rusanu
HIVE-7845 shows how an exception is being thrown when
org.apache.hadoop.util.Shell is being used as a library, not as part of a
deployed Hadoop environment.
{code}
13:20:00 [ERROR pool-2-thread-4 Shell.getWinUtilsPath] Failed to locate the
winutils binary in the hadoop binary path
java.io.IOException: Could not locate executable null\bin\winutils.exe in the
Hadoop binaries.
at
org.apache.hadoop.util.Shell.getQualifiedBinPath(Shell.java:324)
at org.apache.hadoop.util.Shell.getWinUtilsPath(Shell.java:339)
at org.apache.hadoop.util.Shell.clinit(Shell.java:332)
at
org.apache.hadoop.hive.conf.HiveConf$ConfVars.findHadoopBinary(HiveConf.java:918)
at
org.apache.hadoop.hive.conf.HiveConf$ConfVars.clinit(HiveConf.java:228)
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (HADOOP-11004) NFS gateway doesn't respect HDFS extended ACLs
Hari Sekhon created HADOOP-11004: Summary: NFS gateway doesn't respect HDFS extended ACLs Key: HADOOP-11004 URL: https://issues.apache.org/jira/browse/HADOOP-11004 Project: Hadoop Common Issue Type: Bug Components: nfs, security Affects Versions: 2.4.0 Environment: HDP 2.1 Reporter: Hari Sekhon I'm aware that the NFS gateway to HDFS doesn't work with secondary groups until Hadoop 2.5 (HADOOP-10701) but I've also found that when setting extended ACLs to allow the primary group of my regular user account I'm still unable to access that directory in HDFS via the NFS gateway's mount point, although I can via hadoop fs commands, indicating the NFS gateway isn't respecting with HDFS extended ACLs. Nor do the existence of extended ACLS show up via a plus sign after the rwx bits in the NFS directory listing as they do in hadoop fs listing or as regular Linux extended ACLs both do. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: Missing Snapshots for 2.5.0
Thanks for reporting this, Mark. It appears the artifacts are published to https://repository.apache.org/content/repositories/releases/org/apache/hadoop/hadoop-common/2.5.0/, but haven't propagated to http://central.maven.org/maven2/org/apache/hadoop/hadoop-common/ I am following up on this, and will report back once I know more. On Mon, Aug 25, 2014 at 6:40 PM, Tsuyoshi OZAWA ozawa.tsuyo...@gmail.com wrote: Hi Mark, Thanks for your reporting. I also confirmed that we cannot access jars of Hadoop 2.5.0. Karthik, could you check this problem? Thanks, - Tsuyoshi On Thu, Aug 21, 2014 at 2:08 AM, Campbell, Mark mark.campb...@xerox.com wrote: It seems that all the needed archives (yard, mapreduce, etc) are missing the 2.5.0 build folders. My Hadoop 2.5.0 fails at the final build because none of the dependences can be found. Version 2.6.0 does seem to be in the list, however no binaries are available that I can see. Please advise. Cheers, Mark Path /org/apache/hadoop/hadoop-mapreduce-client-app/2.5.0-SNAPSHOT/ not found in local storage of repository Snapshots [id=snapshots] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/hadoop/hadoop-mapreduce-client-app/2.5.0/hadoop-mapreduce-client-app-2.5.0.pom Downloading: http://repo.maven.apache.org/maven2/org/apache/hadoop/hadoop-mapreduce-client-app/2.5.0/hadoop-mapreduce-client-app-2.5.0.pom [WARNING] The POM for org.apache.hadoop:hadoop-mapreduce-client-app:jar:2.5.0 is missing, no dependency information available Downloading: https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-yarn-api/2.5.0/hadoop-yarn-api-2.5.0.pom Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/hadoop/hadoop-yarn-api/2.5.0/hadoop-yarn-api-2.5.0.pom Downloading: http://repo.maven.apache.org/maven2/org/apache/hadoop/hadoop-yarn-api/2.5.0/hadoop-yarn-api-2.5.0.pom [WARNING] The POM for org.apache.hadoop:hadoop-yarn-api:jar:2.5.0 is missing, no dependency information available Downloading: https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-common/2.5.0/hadoop-common-2.5.0.jar Downloading: https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-mapreduce-client-app/2.5.0/hadoop-mapreduce-client-app-2.5.0.jar -- - Tsuyoshi
Re: Updates on migration to git
Last I heard, the import is still going on and appears closer to getting done. Thanks for your patience with the migration. I ll update you as and when there is something. Eventually, the git repo should be at the location in the wiki. On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla ka...@cloudera.com wrote: Thanks for bringing these points up, Zhijie. By the way, a revised How-to-commit wiki is at: https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to make changes and improve it. On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen zs...@hortonworks.com wrote: Do we have any convention about user.name and user.email? For example, we'd like to use @apache.org for the email. May be, we can ask people to use project-specific configs here and use their real name and @apache.org address. Is there any downside to letting people use their global values for these configs? Moreover, do we want to use --author=Author Name em...@address.com when committing on behalf of a particular contributor? Fetching the email-address is complicated here. Should we use the contributor's email from JIRA? What if that is not their @apache address? On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla ka...@cloudera.com wrote: Thanks for your input, Steve. Sorry for sending the email out that late, I sent it as soon as I could. On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran ste...@hortonworks.com wrote: just caught up with this after some offlininess...15:48 PST is too late for me. I'd be -1 to a change to master because of that risk that it does break existing code -especially people that have trunk off the git mirrors and automated builds/merges to go with it. Fair enough. It makes sense to leave it as trunk, unless someone is against it being trunk. master may be viewed as the official git way, but it doesn't have to be. For git-flow workflows (which we use in slider) master/ is for releases, develop/ for dev. On 24 August 2014 02:31, Karthik Kambatla ka...@cloudera.com wrote: Couple of things: 1. Since no one expressed any reservations against doing this on Sunday or renaming trunk to master, I ll go ahead and confirm that. I think that serves us better in the long run. 2. Arpit brought up the precommit builds - we should definitely fix them as soon as we can. I understand Giri maintains those builds, do we have anyone else who has access in case Giri is not reachable? Giri - please shout out if you can help us with this either on Sunday or Monday. Thanks Karthik On Fri, Aug 22, 2014 at 3:50 PM, Karthik Kambatla ka...@cloudera.com wrote: Also, does anyone know what we use for integration between JIRA and svn? I am assuming svn2jira. On Fri, Aug 22, 2014 at 3:48 PM, Karthik Kambatla ka...@cloudera.com wrote: Hi folks, For the SCM migration, feel free to follow https://issues.apache.org/jira/browse/INFRA-8195 Most of this is planned to be handled this Sunday. As a result, the subversion repository would be read-only. If this is a major issue for you, please shout out. Daniel Gruno, the one helping us with the migration, was asking if we are open to renaming trunk to master to better conform to git lingo. I am tempted to say yes, but wanted to check. Would greatly appreciate any help with checking the git repo has everything. Thanks Karthik -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. -- Zhijie Shen Hortonworks Inc. http://hortonworks.com/ -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: Updates on migration to git
Karthik, I would like to see detailed information on how this migration will be done, how it will affect the existing project and commit process. This should be done in a document that can be reviewed instead of in an email thread on an ad-hoc basis. Was there any voting on this in PMC and should we have a vote to ensure everyone is one the same page on doing this and how to go about it? Regards, Suresh On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla ka...@cloudera.com wrote: Last I heard, the import is still going on and appears closer to getting done. Thanks for your patience with the migration. I ll update you as and when there is something. Eventually, the git repo should be at the location in the wiki. On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla ka...@cloudera.com wrote: Thanks for bringing these points up, Zhijie. By the way, a revised How-to-commit wiki is at: https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to make changes and improve it. On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen zs...@hortonworks.com wrote: Do we have any convention about user.name and user.email? For example, we'd like to use @apache.org for the email. May be, we can ask people to use project-specific configs here and use their real name and @apache.org address. Is there any downside to letting people use their global values for these configs? Moreover, do we want to use --author=Author Name em...@address.com when committing on behalf of a particular contributor? Fetching the email-address is complicated here. Should we use the contributor's email from JIRA? What if that is not their @apache address? On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla ka...@cloudera.com wrote: Thanks for your input, Steve. Sorry for sending the email out that late, I sent it as soon as I could. On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran ste...@hortonworks.com wrote: just caught up with this after some offlininess...15:48 PST is too late for me. I'd be -1 to a change to master because of that risk that it does break existing code -especially people that have trunk off the git mirrors and automated builds/merges to go with it. Fair enough. It makes sense to leave it as trunk, unless someone is against it being trunk. master may be viewed as the official git way, but it doesn't have to be. For git-flow workflows (which we use in slider) master/ is for releases, develop/ for dev. On 24 August 2014 02:31, Karthik Kambatla ka...@cloudera.com wrote: Couple of things: 1. Since no one expressed any reservations against doing this on Sunday or renaming trunk to master, I ll go ahead and confirm that. I think that serves us better in the long run. 2. Arpit brought up the precommit builds - we should definitely fix them as soon as we can. I understand Giri maintains those builds, do we have anyone else who has access in case Giri is not reachable? Giri - please shout out if you can help us with this either on Sunday or Monday. Thanks Karthik On Fri, Aug 22, 2014 at 3:50 PM, Karthik Kambatla ka...@cloudera.com wrote: Also, does anyone know what we use for integration between JIRA and svn? I am assuming svn2jira. On Fri, Aug 22, 2014 at 3:48 PM, Karthik Kambatla ka...@cloudera.com wrote: Hi folks, For the SCM migration, feel free to follow https://issues.apache.org/jira/browse/INFRA-8195 Most of this is planned to be handled this Sunday. As a result, the subversion repository would be read-only. If this is a major issue for you, please shout out. Daniel Gruno, the one helping us with the migration, was asking if we are open to renaming trunk to master to better conform to git lingo. I am tempted to say yes, but wanted to check. Would greatly appreciate any help with checking the git repo has everything. Thanks Karthik -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. -- Zhijie
Re: Updates on migration to git
Hi Suresh There was one vote thread on whether to migrate to git, and the implications to the commit process for individual patches and feature branches - https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html . Prior to that, there was a discuss thread on the same topic. As INFRA handles the actual migration from subversion to git, the vote didn't include those specifics. The migration is going on as we speak (See INFRA-8195). The initial expectation was that the migration would be done in a few hours, but it has been several hours and the last I heard the import was still running. I have elaborated on the points in the vote thread and drafted up a wiki page on how-to-commit - https://wiki.apache.org/hadoop/HowToCommitWithGit . We can work on improving this further and call a vote thread on those items if need be. Thanks Karthik On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas sur...@hortonworks.com wrote: Karthik, I would like to see detailed information on how this migration will be done, how it will affect the existing project and commit process. This should be done in a document that can be reviewed instead of in an email thread on an ad-hoc basis. Was there any voting on this in PMC and should we have a vote to ensure everyone is one the same page on doing this and how to go about it? Regards, Suresh On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla ka...@cloudera.com wrote: Last I heard, the import is still going on and appears closer to getting done. Thanks for your patience with the migration. I ll update you as and when there is something. Eventually, the git repo should be at the location in the wiki. On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla ka...@cloudera.com wrote: Thanks for bringing these points up, Zhijie. By the way, a revised How-to-commit wiki is at: https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to make changes and improve it. On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen zs...@hortonworks.com wrote: Do we have any convention about user.name and user.email? For example, we'd like to use @apache.org for the email. May be, we can ask people to use project-specific configs here and use their real name and @apache.org address. Is there any downside to letting people use their global values for these configs? Moreover, do we want to use --author=Author Name em...@address.com when committing on behalf of a particular contributor? Fetching the email-address is complicated here. Should we use the contributor's email from JIRA? What if that is not their @apache address? On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla ka...@cloudera.com wrote: Thanks for your input, Steve. Sorry for sending the email out that late, I sent it as soon as I could. On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran ste...@hortonworks.com wrote: just caught up with this after some offlininess...15:48 PST is too late for me. I'd be -1 to a change to master because of that risk that it does break existing code -especially people that have trunk off the git mirrors and automated builds/merges to go with it. Fair enough. It makes sense to leave it as trunk, unless someone is against it being trunk. master may be viewed as the official git way, but it doesn't have to be. For git-flow workflows (which we use in slider) master/ is for releases, develop/ for dev. On 24 August 2014 02:31, Karthik Kambatla ka...@cloudera.com wrote: Couple of things: 1. Since no one expressed any reservations against doing this on Sunday or renaming trunk to master, I ll go ahead and confirm that. I think that serves us better in the long run. 2. Arpit brought up the precommit builds - we should definitely fix them as soon as we can. I understand Giri maintains those builds, do we have anyone else who has access in case Giri is not reachable? Giri - please shout out if you can help us with this either on Sunday or Monday. Thanks Karthik On Fri, Aug 22, 2014 at 3:50 PM, Karthik Kambatla ka...@cloudera.com wrote: Also, does anyone know what we use for integration between JIRA and svn? I am assuming svn2jira. On Fri, Aug 22, 2014 at 3:48 PM, Karthik Kambatla ka...@cloudera.com wrote: Hi folks, For the SCM migration, feel free to follow https://issues.apache.org/jira/browse/INFRA-8195 Most of this is planned to be handled this Sunday. As a result, the subversion repository would be read-only. If this
Re: Updates on migration to git
The git repository is now ready for inspection. I ll take a look shortly, but it would be great if a few others could too. Once we are okay with it, we can ask it to be writable. On Tuesday, August 26, 2014, Karthik Kambatla ka...@cloudera.com wrote: Hi Suresh There was one vote thread on whether to migrate to git, and the implications to the commit process for individual patches and feature branches - https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html . Prior to that, there was a discuss thread on the same topic. As INFRA handles the actual migration from subversion to git, the vote didn't include those specifics. The migration is going on as we speak (See INFRA-8195). The initial expectation was that the migration would be done in a few hours, but it has been several hours and the last I heard the import was still running. I have elaborated on the points in the vote thread and drafted up a wiki page on how-to-commit - https://wiki.apache.org/hadoop/HowToCommitWithGit . We can work on improving this further and call a vote thread on those items if need be. Thanks Karthik On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas sur...@hortonworks.com javascript:_e(%7B%7D,'cvml','sur...@hortonworks.com'); wrote: Karthik, I would like to see detailed information on how this migration will be done, how it will affect the existing project and commit process. This should be done in a document that can be reviewed instead of in an email thread on an ad-hoc basis. Was there any voting on this in PMC and should we have a vote to ensure everyone is one the same page on doing this and how to go about it? Regards, Suresh On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla ka...@cloudera.com javascript:_e(%7B%7D,'cvml','ka...@cloudera.com'); wrote: Last I heard, the import is still going on and appears closer to getting done. Thanks for your patience with the migration. I ll update you as and when there is something. Eventually, the git repo should be at the location in the wiki. On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla ka...@cloudera.com javascript:_e(%7B%7D,'cvml','ka...@cloudera.com'); wrote: Thanks for bringing these points up, Zhijie. By the way, a revised How-to-commit wiki is at: https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to make changes and improve it. On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen zs...@hortonworks.com javascript:_e(%7B%7D,'cvml','zs...@hortonworks.com'); wrote: Do we have any convention about user.name and user.email? For example, we'd like to use @apache.org for the email. May be, we can ask people to use project-specific configs here and use their real name and @apache.org address. Is there any downside to letting people use their global values for these configs? Moreover, do we want to use --author=Author Name em...@address.com javascript:_e(%7B%7D,'cvml','em...@address.com'); when committing on behalf of a particular contributor? Fetching the email-address is complicated here. Should we use the contributor's email from JIRA? What if that is not their @apache address? On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla ka...@cloudera.com javascript:_e(%7B%7D,'cvml','ka...@cloudera.com'); wrote: Thanks for your input, Steve. Sorry for sending the email out that late, I sent it as soon as I could. On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran ste...@hortonworks.com javascript:_e(%7B%7D,'cvml','ste...@hortonworks.com'); wrote: just caught up with this after some offlininess...15:48 PST is too late for me. I'd be -1 to a change to master because of that risk that it does break existing code -especially people that have trunk off the git mirrors and automated builds/merges to go with it. Fair enough. It makes sense to leave it as trunk, unless someone is against it being trunk. master may be viewed as the official git way, but it doesn't have to be. For git-flow workflows (which we use in slider) master/ is for releases, develop/ for dev. On 24 August 2014 02:31, Karthik Kambatla ka...@cloudera.com javascript:_e(%7B%7D,'cvml','ka...@cloudera.com'); wrote: Couple of things: 1. Since no one expressed any reservations against doing this on Sunday or renaming trunk to master, I ll go ahead and confirm that. I think that serves us better in the long run. 2. Arpit brought up the precommit builds - we should definitely fix them as soon as we can. I understand Giri maintains those builds, do we have anyone else who has access in case Giri is not reachable? Giri - please shout out if you can help us with
[jira] [Created] (HADOOP-11005) Fix HTTP content type for ReconfigurationServlet
Lei (Eddy) Xu created HADOOP-11005:
--
Summary: Fix HTTP content type for ReconfigurationServlet
Key: HADOOP-11005
URL: https://issues.apache.org/jira/browse/HADOOP-11005
Project: Hadoop Common
Issue Type: Bug
Components: conf
Affects Versions: 2.5.0
Reporter: Lei (Eddy) Xu
Assignee: Lei (Eddy) Xu
Priority: Minor
The reconfiguration framework introduced from HDFS-7001 supports reload
configuration from HTTP servlet, using {{ReconfigurableServlet}}.
{{ReconfigurableServlet}} processes a HTTP GET request to list the differences
between old and new configurations in HTML, with a form that allows the user to
submit to confirm the configuration changes. However since the response lacks
HTTP content-type, the browser renders the page as text file, which makes it
impossible to submit the form.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (HADOOP-11006) cp should automatically use /.reserved/raw when run by the superuser
Charles Lamb created HADOOP-11006: - Summary: cp should automatically use /.reserved/raw when run by the superuser Key: HADOOP-11006 URL: https://issues.apache.org/jira/browse/HADOOP-11006 Project: Hadoop Common Issue Type: Bug Affects Versions: 3.0.0 Reporter: Charles Lamb Assignee: Charles Lamb On HDFS-6134, Sanjay Radia asked for cp to automatically prepend /.reserved/raw if the cp is being performed by the superuser and /.reserved/raw is supported by both the source and destination filesystems. This behavior only occurs if none of the src and target pathnames are /.reserved/raw. The -disablereservedraw flag can be used to disable this option. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: Updates on migration to git
Hi, Great to see the move towards git. In terms of documentation could you please include the way binary files should be included in a patch (see this discussion https://www.mail-archive.com/common-dev%40hadoop.apache.org/msg13166.html ) and update http://wiki.apache.org/hadoop/GitAndHadoop too (this one still talks about the time when there were 3 projects). Thanks. -- Best regards / Met vriendelijke groeten, Niels Basjes
Re: Updates on migration to git
I compared the new asf git repo against the svn and github repos (mirrored from svn). Here is what I see: - for i in *; do git diff $i ../hadoop-github/$i; done showed no differences between the two. So, I think all the source is there. - The branches match - All svn tags exist in git, but git has a few more. These additional ones are those that we deleted from svn. - git rev-list --remotes | wc -l shows 27006 revisions in the new git repo and 29549 revisions in the github repo. Checking with Daniel, he said the git svn import works differently compared to the git mirroring. Are we comfortable with making the git repo writable under these conditions? I ll let other people poke around and report. Thanks for your cooperation, Karthik On Tue, Aug 26, 2014 at 1:19 PM, Karthik Kambatla ka...@cloudera.com wrote: The git repository is now ready for inspection. I ll take a look shortly, but it would be great if a few others could too. Once we are okay with it, we can ask it to be writable. On Tuesday, August 26, 2014, Karthik Kambatla ka...@cloudera.com wrote: Hi Suresh There was one vote thread on whether to migrate to git, and the implications to the commit process for individual patches and feature branches - https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html . Prior to that, there was a discuss thread on the same topic. As INFRA handles the actual migration from subversion to git, the vote didn't include those specifics. The migration is going on as we speak (See INFRA-8195). The initial expectation was that the migration would be done in a few hours, but it has been several hours and the last I heard the import was still running. I have elaborated on the points in the vote thread and drafted up a wiki page on how-to-commit - https://wiki.apache.org/hadoop/HowToCommitWithGit . We can work on improving this further and call a vote thread on those items if need be. Thanks Karthik On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas sur...@hortonworks.com wrote: Karthik, I would like to see detailed information on how this migration will be done, how it will affect the existing project and commit process. This should be done in a document that can be reviewed instead of in an email thread on an ad-hoc basis. Was there any voting on this in PMC and should we have a vote to ensure everyone is one the same page on doing this and how to go about it? Regards, Suresh On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla ka...@cloudera.com wrote: Last I heard, the import is still going on and appears closer to getting done. Thanks for your patience with the migration. I ll update you as and when there is something. Eventually, the git repo should be at the location in the wiki. On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla ka...@cloudera.com wrote: Thanks for bringing these points up, Zhijie. By the way, a revised How-to-commit wiki is at: https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to make changes and improve it. On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen zs...@hortonworks.com wrote: Do we have any convention about user.name and user.email? For example, we'd like to use @apache.org for the email. May be, we can ask people to use project-specific configs here and use their real name and @apache.org address. Is there any downside to letting people use their global values for these configs? Moreover, do we want to use --author=Author Name em...@address.com when committing on behalf of a particular contributor? Fetching the email-address is complicated here. Should we use the contributor's email from JIRA? What if that is not their @apache address? On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla ka...@cloudera.com wrote: Thanks for your input, Steve. Sorry for sending the email out that late, I sent it as soon as I could. On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran ste...@hortonworks.com wrote: just caught up with this after some offlininess...15:48 PST is too late for me. I'd be -1 to a change to master because of that risk that it does break existing code -especially people that have trunk off the git mirrors and automated builds/merges to go with it. Fair enough. It makes sense to leave it as trunk, unless someone is against it being trunk. master may be viewed as the official git way, but it doesn't have to be. For git-flow workflows (which we use in slider) master/ is for releases, develop/ for dev. On 24 August 2014 02:31, Karthik Kambatla ka...@cloudera.com wrote: Couple of things: 1. Since no one expressed any reservations against doing this on Sunday or renaming trunk
[jira] [Created] (HADOOP-11007) Reinstate building of ant tasks support
Jason Lowe created HADOOP-11007: --- Summary: Reinstate building of ant tasks support Key: HADOOP-11007 URL: https://issues.apache.org/jira/browse/HADOOP-11007 Project: Hadoop Common Issue Type: Improvement Components: build, fs Affects Versions: 2.5.0 Reporter: Jason Lowe Assignee: Jason Lowe The ant tasks support from HADOOP-1508 is still present under hadoop-hdfs/src/ant/ but is no longer being built. It would be nice if this was reinstated in the build and distributed as part of the release. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: Updates on migration to git
I've just did some work on top of trunk and branch-2, all good. Thanks Karthik. On Tue, Aug 26, 2014 at 2:26 PM, Karthik Kambatla ka...@cloudera.com wrote: I compared the new asf git repo against the svn and github repos (mirrored from svn). Here is what I see: - for i in *; do git diff $i ../hadoop-github/$i; done showed no differences between the two. So, I think all the source is there. - The branches match - All svn tags exist in git, but git has a few more. These additional ones are those that we deleted from svn. - git rev-list --remotes | wc -l shows 27006 revisions in the new git repo and 29549 revisions in the github repo. Checking with Daniel, he said the git svn import works differently compared to the git mirroring. Are we comfortable with making the git repo writable under these conditions? I ll let other people poke around and report. Thanks for your cooperation, Karthik On Tue, Aug 26, 2014 at 1:19 PM, Karthik Kambatla ka...@cloudera.com wrote: The git repository is now ready for inspection. I ll take a look shortly, but it would be great if a few others could too. Once we are okay with it, we can ask it to be writable. On Tuesday, August 26, 2014, Karthik Kambatla ka...@cloudera.com wrote: Hi Suresh There was one vote thread on whether to migrate to git, and the implications to the commit process for individual patches and feature branches - https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html . Prior to that, there was a discuss thread on the same topic. As INFRA handles the actual migration from subversion to git, the vote didn't include those specifics. The migration is going on as we speak (See INFRA-8195). The initial expectation was that the migration would be done in a few hours, but it has been several hours and the last I heard the import was still running. I have elaborated on the points in the vote thread and drafted up a wiki page on how-to-commit - https://wiki.apache.org/hadoop/HowToCommitWithGit . We can work on improving this further and call a vote thread on those items if need be. Thanks Karthik On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas sur...@hortonworks.com wrote: Karthik, I would like to see detailed information on how this migration will be done, how it will affect the existing project and commit process. This should be done in a document that can be reviewed instead of in an email thread on an ad-hoc basis. Was there any voting on this in PMC and should we have a vote to ensure everyone is one the same page on doing this and how to go about it? Regards, Suresh On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla ka...@cloudera.com wrote: Last I heard, the import is still going on and appears closer to getting done. Thanks for your patience with the migration. I ll update you as and when there is something. Eventually, the git repo should be at the location in the wiki. On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla ka...@cloudera.com wrote: Thanks for bringing these points up, Zhijie. By the way, a revised How-to-commit wiki is at: https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to make changes and improve it. On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen zs...@hortonworks.com wrote: Do we have any convention about user.name and user.email? For example, we'd like to use @apache.org for the email. May be, we can ask people to use project-specific configs here and use their real name and @apache.org address. Is there any downside to letting people use their global values for these configs? Moreover, do we want to use --author=Author Name em...@address.com when committing on behalf of a particular contributor? Fetching the email-address is complicated here. Should we use the contributor's email from JIRA? What if that is not their @apache address? On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla ka...@cloudera.com wrote: Thanks for your input, Steve. Sorry for sending the email out that late, I sent it as soon as I could. On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran ste...@hortonworks.com wrote: just caught up with this after some offlininess...15:48 PST is too late for me. I'd be -1 to a change to master because of that risk that it does break existing code -especially people that have trunk off the git mirrors and automated builds/merges to go with it. Fair enough. It makes sense to leave it as trunk, unless someone is against it being trunk. master may be viewed as the official git way, but it doesn't have to be. For
Re: Updates on migration to git
Did a build. Started some stuff. Have a patch ready to be committed. ;) Thanks Karthik and Daniel! On Aug 26, 2014, at 2:26 PM, Karthik Kambatla ka...@cloudera.com wrote: I compared the new asf git repo against the svn and github repos (mirrored from svn). Here is what I see: - for i in *; do git diff $i ../hadoop-github/$i; done showed no differences between the two. So, I think all the source is there. - The branches match - All svn tags exist in git, but git has a few more. These additional ones are those that we deleted from svn. - git rev-list --remotes | wc -l shows 27006 revisions in the new git repo and 29549 revisions in the github repo. Checking with Daniel, he said the git svn import works differently compared to the git mirroring. Are we comfortable with making the git repo writable under these conditions? I ll let other people poke around and report. Thanks for your cooperation, Karthik On Tue, Aug 26, 2014 at 1:19 PM, Karthik Kambatla ka...@cloudera.com wrote: The git repository is now ready for inspection. I ll take a look shortly, but it would be great if a few others could too. Once we are okay with it, we can ask it to be writable. On Tuesday, August 26, 2014, Karthik Kambatla ka...@cloudera.com wrote: Hi Suresh There was one vote thread on whether to migrate to git, and the implications to the commit process for individual patches and feature branches - https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html . Prior to that, there was a discuss thread on the same topic. As INFRA handles the actual migration from subversion to git, the vote didn't include those specifics. The migration is going on as we speak (See INFRA-8195). The initial expectation was that the migration would be done in a few hours, but it has been several hours and the last I heard the import was still running. I have elaborated on the points in the vote thread and drafted up a wiki page on how-to-commit - https://wiki.apache.org/hadoop/HowToCommitWithGit . We can work on improving this further and call a vote thread on those items if need be. Thanks Karthik On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas sur...@hortonworks.com wrote: Karthik, I would like to see detailed information on how this migration will be done, how it will affect the existing project and commit process. This should be done in a document that can be reviewed instead of in an email thread on an ad-hoc basis. Was there any voting on this in PMC and should we have a vote to ensure everyone is one the same page on doing this and how to go about it? Regards, Suresh On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla ka...@cloudera.com wrote: Last I heard, the import is still going on and appears closer to getting done. Thanks for your patience with the migration. I ll update you as and when there is something. Eventually, the git repo should be at the location in the wiki. On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla ka...@cloudera.com wrote: Thanks for bringing these points up, Zhijie. By the way, a revised How-to-commit wiki is at: https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to make changes and improve it. On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen zs...@hortonworks.com wrote: Do we have any convention about user.name and user.email? For example, we'd like to use @apache.org for the email. May be, we can ask people to use project-specific configs here and use their real name and @apache.org address. Is there any downside to letting people use their global values for these configs? Moreover, do we want to use --author=Author Name em...@address.com when committing on behalf of a particular contributor? Fetching the email-address is complicated here. Should we use the contributor's email from JIRA? What if that is not their @apache address? On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla ka...@cloudera.com wrote: Thanks for your input, Steve. Sorry for sending the email out that late, I sent it as soon as I could. On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran ste...@hortonworks.com wrote: just caught up with this after some offlininess...15:48 PST is too late for me. I'd be -1 to a change to master because of that risk that it does break existing code -especially people that have trunk off the git mirrors and automated builds/merges to go with it. Fair enough. It makes sense to leave it as trunk, unless someone is against it being trunk. master may be viewed as the official git way, but it doesn't have to be. For git-flow workflows (which we use in slider) master/ is for releases, develop/ for dev. On 24 August 2014 02:31, Karthik Kambatla ka...@cloudera.com wrote: Couple of things: 1. Since no one expressed any reservations against doing this on Sunday or
[jira] [Resolved] (HADOOP-11002) shell escapes are incompatible with previous releases
[
https://issues.apache.org/jira/browse/HADOOP-11002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-11002.
---
Resolution: Fixed
Fix Version/s: 3.0.0
Thanks! I'll commit this as soon as git opens up!
shell escapes are incompatible with previous releases
-
Key: HADOOP-11002
URL: https://issues.apache.org/jira/browse/HADOOP-11002
Project: Hadoop Common
Issue Type: Bug
Components: scripts
Reporter: Allen Wittenauer
Labels: regression
Fix For: 3.0.0
Attachments: HADOOP-11002.patch
Post-HADOOP-9902, the following in xyz_OPTS doesn't work without being
escaped:
{code}
-XX:HeapDumpPath=./java_pid_pid.hprof
{code}
This is a bit of surprising behavior to the users. The breakage is directly
result of the code that fixes spaces in directories. Since it is much more
likely to hit weird metacharacters in shell than have directories with
spaces, that part of HADOOP-9902 needs to get replaced.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Re: Updates on migration to git
:) I missed that voting thread. Thanks Karthik! Arpit Agarwal also told me offline that commit process has been updated - https://wiki.apache.org/hadoop/HowToCommit and git setup also has also been documented - https://www.apache.org/dev/git.html. Thanks Arpit! On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas sur...@hortonworks.com wrote: Karthik, I would like to see detailed information on how this migration will be done, how it will affect the existing project and commit process. This should be done in a document that can be reviewed instead of in an email thread on an ad-hoc basis. Was there any voting on this in PMC and should we have a vote to ensure everyone is one the same page on doing this and how to go about it? Regards, Suresh On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla ka...@cloudera.com wrote: Last I heard, the import is still going on and appears closer to getting done. Thanks for your patience with the migration. I ll update you as and when there is something. Eventually, the git repo should be at the location in the wiki. On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla ka...@cloudera.com wrote: Thanks for bringing these points up, Zhijie. By the way, a revised How-to-commit wiki is at: https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to make changes and improve it. On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen zs...@hortonworks.com wrote: Do we have any convention about user.name and user.email? For example, we'd like to use @apache.org for the email. May be, we can ask people to use project-specific configs here and use their real name and @apache.org address. Is there any downside to letting people use their global values for these configs? Moreover, do we want to use --author=Author Name em...@address.com when committing on behalf of a particular contributor? Fetching the email-address is complicated here. Should we use the contributor's email from JIRA? What if that is not their @apache address? On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla ka...@cloudera.com wrote: Thanks for your input, Steve. Sorry for sending the email out that late, I sent it as soon as I could. On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran ste...@hortonworks.com wrote: just caught up with this after some offlininess...15:48 PST is too late for me. I'd be -1 to a change to master because of that risk that it does break existing code -especially people that have trunk off the git mirrors and automated builds/merges to go with it. Fair enough. It makes sense to leave it as trunk, unless someone is against it being trunk. master may be viewed as the official git way, but it doesn't have to be. For git-flow workflows (which we use in slider) master/ is for releases, develop/ for dev. On 24 August 2014 02:31, Karthik Kambatla ka...@cloudera.com wrote: Couple of things: 1. Since no one expressed any reservations against doing this on Sunday or renaming trunk to master, I ll go ahead and confirm that. I think that serves us better in the long run. 2. Arpit brought up the precommit builds - we should definitely fix them as soon as we can. I understand Giri maintains those builds, do we have anyone else who has access in case Giri is not reachable? Giri - please shout out if you can help us with this either on Sunday or Monday. Thanks Karthik On Fri, Aug 22, 2014 at 3:50 PM, Karthik Kambatla ka...@cloudera.com wrote: Also, does anyone know what we use for integration between JIRA and svn? I am assuming svn2jira. On Fri, Aug 22, 2014 at 3:48 PM, Karthik Kambatla ka...@cloudera.com wrote: Hi folks, For the SCM migration, feel free to follow https://issues.apache.org/jira/browse/INFRA-8195 Most of this is planned to be handled this Sunday. As a result, the subversion repository would be read-only. If this is a major issue for you, please shout out. Daniel Gruno, the one helping us with the migration, was asking if we are open to renaming trunk to master to better conform to git lingo. I am tempted to say yes, but wanted to check. Would greatly appreciate any help with checking the git repo has everything. Thanks Karthik -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message
Re: Updates on migration to git
I cloned the new repo, built trunk and branch-2, verified all the branches are present. Also checked a few branches and the recent commit history matches our existing repo. Everything looks good so far. On Tue, Aug 26, 2014 at 1:19 PM, Karthik Kambatla ka...@cloudera.com wrote: The git repository is now ready for inspection. I ll take a look shortly, but it would be great if a few others could too. Once we are okay with it, we can ask it to be writable. On Tuesday, August 26, 2014, Karthik Kambatla ka...@cloudera.com wrote: Hi Suresh There was one vote thread on whether to migrate to git, and the implications to the commit process for individual patches and feature branches - https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html . Prior to that, there was a discuss thread on the same topic. As INFRA handles the actual migration from subversion to git, the vote didn't include those specifics. The migration is going on as we speak (See INFRA-8195). The initial expectation was that the migration would be done in a few hours, but it has been several hours and the last I heard the import was still running. I have elaborated on the points in the vote thread and drafted up a wiki page on how-to-commit - https://wiki.apache.org/hadoop/HowToCommitWithGit . We can work on improving this further and call a vote thread on those items if need be. Thanks Karthik On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas sur...@hortonworks.com javascript:_e(%7B%7D,'cvml','sur...@hortonworks.com'); wrote: Karthik, I would like to see detailed information on how this migration will be done, how it will affect the existing project and commit process. This should be done in a document that can be reviewed instead of in an email thread on an ad-hoc basis. Was there any voting on this in PMC and should we have a vote to ensure everyone is one the same page on doing this and how to go about it? Regards, Suresh On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla ka...@cloudera.com javascript:_e(%7B%7D,'cvml','ka...@cloudera.com'); wrote: Last I heard, the import is still going on and appears closer to getting done. Thanks for your patience with the migration. I ll update you as and when there is something. Eventually, the git repo should be at the location in the wiki. On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla ka...@cloudera.com javascript:_e(%7B%7D,'cvml','ka...@cloudera.com'); wrote: Thanks for bringing these points up, Zhijie. By the way, a revised How-to-commit wiki is at: https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to make changes and improve it. On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen zs...@hortonworks.com javascript:_e(%7B%7D,'cvml','zs...@hortonworks.com'); wrote: Do we have any convention about user.name and user.email? For example, we'd like to use @apache.org for the email. May be, we can ask people to use project-specific configs here and use their real name and @apache.org address. Is there any downside to letting people use their global values for these configs? Moreover, do we want to use --author=Author Name em...@address.com javascript:_e(%7B%7D,'cvml','em...@address.com'); when committing on behalf of a particular contributor? Fetching the email-address is complicated here. Should we use the contributor's email from JIRA? What if that is not their @apache address? On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla ka...@cloudera.com javascript:_e(%7B%7D,'cvml','ka...@cloudera.com '); wrote: Thanks for your input, Steve. Sorry for sending the email out that late, I sent it as soon as I could. On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran ste...@hortonworks.com javascript:_e(%7B%7D,'cvml','ste...@hortonworks.com'); wrote: just caught up with this after some offlininess...15:48 PST is too late for me. I'd be -1 to a change to master because of that risk that it does break existing code -especially people that have trunk off the git mirrors and automated builds/merges to go with it. Fair enough. It makes sense to leave it as trunk, unless someone is against it being trunk. master may be viewed as the official git way, but it doesn't have to be. For git-flow workflows (which we use in slider) master/ is for releases, develop/ for dev. On 24 August 2014 02:31, Karthik Kambatla ka...@cloudera.com javascript:_e(%7B%7D,'cvml','ka...@cloudera.com'); wrote: Couple of things: 1. Since no one expressed any reservations against doing this on
Re: Updates on migration to git
Looks like our git repo is good to go. On INFRA-8195, I am asking Daniel to enable writing to it. In case you find any issues, please comment on the JIRA. Thanks Karthik On Tue, Aug 26, 2014 at 3:28 PM, Arpit Agarwal aagar...@hortonworks.com wrote: I cloned the new repo, built trunk and branch-2, verified all the branches are present. Also checked a few branches and the recent commit history matches our existing repo. Everything looks good so far. On Tue, Aug 26, 2014 at 1:19 PM, Karthik Kambatla ka...@cloudera.com wrote: The git repository is now ready for inspection. I ll take a look shortly, but it would be great if a few others could too. Once we are okay with it, we can ask it to be writable. On Tuesday, August 26, 2014, Karthik Kambatla ka...@cloudera.com wrote: Hi Suresh There was one vote thread on whether to migrate to git, and the implications to the commit process for individual patches and feature branches - https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html . Prior to that, there was a discuss thread on the same topic. As INFRA handles the actual migration from subversion to git, the vote didn't include those specifics. The migration is going on as we speak (See INFRA-8195). The initial expectation was that the migration would be done in a few hours, but it has been several hours and the last I heard the import was still running. I have elaborated on the points in the vote thread and drafted up a wiki page on how-to-commit - https://wiki.apache.org/hadoop/HowToCommitWithGit . We can work on improving this further and call a vote thread on those items if need be. Thanks Karthik On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas sur...@hortonworks.com javascript:_e(%7B%7D,'cvml','sur...@hortonworks.com'); wrote: Karthik, I would like to see detailed information on how this migration will be done, how it will affect the existing project and commit process. This should be done in a document that can be reviewed instead of in an email thread on an ad-hoc basis. Was there any voting on this in PMC and should we have a vote to ensure everyone is one the same page on doing this and how to go about it? Regards, Suresh On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla ka...@cloudera.com javascript:_e(%7B%7D,'cvml','ka...@cloudera.com'); wrote: Last I heard, the import is still going on and appears closer to getting done. Thanks for your patience with the migration. I ll update you as and when there is something. Eventually, the git repo should be at the location in the wiki. On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla ka...@cloudera.com javascript:_e(%7B%7D,'cvml','ka...@cloudera.com'); wrote: Thanks for bringing these points up, Zhijie. By the way, a revised How-to-commit wiki is at: https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to make changes and improve it. On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen zs...@hortonworks.com javascript:_e(%7B%7D,'cvml','zs...@hortonworks.com'); wrote: Do we have any convention about user.name and user.email? For example, we'd like to use @apache.org for the email. May be, we can ask people to use project-specific configs here and use their real name and @apache.org address. Is there any downside to letting people use their global values for these configs? Moreover, do we want to use --author=Author Name em...@address.com javascript:_e(%7B%7D,'cvml','em...@address.com '); when committing on behalf of a particular contributor? Fetching the email-address is complicated here. Should we use the contributor's email from JIRA? What if that is not their @apache address? On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla ka...@cloudera.com javascript:_e(%7B%7D,'cvml','ka...@cloudera.com '); wrote: Thanks for your input, Steve. Sorry for sending the email out that late, I sent it as soon as I could. On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran ste...@hortonworks.com javascript:_e(%7B%7D,'cvml','ste...@hortonworks.com'); wrote: just caught up with this after some offlininess...15:48 PST is too late for me. I'd be -1 to a change to master because of that risk that it does break existing code -especially people that have trunk off the git mirrors and automated builds/merges to go with it. Fair enough. It makes sense to leave it as trunk, unless someone is against it being trunk. master may be viewed as the
[jira] [Created] (HADOOP-11009) Add Timestamp Preservation to DistCp
Gary Steelman created HADOOP-11009: -- Summary: Add Timestamp Preservation to DistCp Key: HADOOP-11009 URL: https://issues.apache.org/jira/browse/HADOOP-11009 Project: Hadoop Common Issue Type: Improvement Components: tools/distcp Affects Versions: 2.4.0 Reporter: Gary Steelman Currently access and modification times are not preserved on files copied using DistCp. This patch adds an option to DistCp for timestamp preservation. The patch ready, but I understand there is a Contributor form I need to sign before I can upload it. Can someone point me in the right direction for this form? Thanks! -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: Updates on migration to git
Hey Karthik, Just to confirm, have we disabled force-push support on the repo? In my experience, especially when a project has committers new to git, force-push support causes more trouble than it's worth. -Todd On Tue, Aug 26, 2014 at 4:39 PM, Karthik Kambatla ka...@cloudera.com wrote: Looks like our git repo is good to go. On INFRA-8195, I am asking Daniel to enable writing to it. In case you find any issues, please comment on the JIRA. Thanks Karthik On Tue, Aug 26, 2014 at 3:28 PM, Arpit Agarwal aagar...@hortonworks.com wrote: I cloned the new repo, built trunk and branch-2, verified all the branches are present. Also checked a few branches and the recent commit history matches our existing repo. Everything looks good so far. On Tue, Aug 26, 2014 at 1:19 PM, Karthik Kambatla ka...@cloudera.com wrote: The git repository is now ready for inspection. I ll take a look shortly, but it would be great if a few others could too. Once we are okay with it, we can ask it to be writable. On Tuesday, August 26, 2014, Karthik Kambatla ka...@cloudera.com wrote: Hi Suresh There was one vote thread on whether to migrate to git, and the implications to the commit process for individual patches and feature branches - https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html . Prior to that, there was a discuss thread on the same topic. As INFRA handles the actual migration from subversion to git, the vote didn't include those specifics. The migration is going on as we speak (See INFRA-8195). The initial expectation was that the migration would be done in a few hours, but it has been several hours and the last I heard the import was still running. I have elaborated on the points in the vote thread and drafted up a wiki page on how-to-commit - https://wiki.apache.org/hadoop/HowToCommitWithGit . We can work on improving this further and call a vote thread on those items if need be. Thanks Karthik On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas sur...@hortonworks.com javascript:_e(%7B%7D,'cvml','sur...@hortonworks.com'); wrote: Karthik, I would like to see detailed information on how this migration will be done, how it will affect the existing project and commit process. This should be done in a document that can be reviewed instead of in an email thread on an ad-hoc basis. Was there any voting on this in PMC and should we have a vote to ensure everyone is one the same page on doing this and how to go about it? Regards, Suresh On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla ka...@cloudera.com javascript:_e(%7B%7D,'cvml','ka...@cloudera.com'); wrote: Last I heard, the import is still going on and appears closer to getting done. Thanks for your patience with the migration. I ll update you as and when there is something. Eventually, the git repo should be at the location in the wiki. On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla ka...@cloudera.com javascript:_e(%7B%7D,'cvml','ka...@cloudera.com'); wrote: Thanks for bringing these points up, Zhijie. By the way, a revised How-to-commit wiki is at: https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to make changes and improve it. On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen zs...@hortonworks.com javascript:_e(%7B%7D,'cvml','zs...@hortonworks.com'); wrote: Do we have any convention about user.name and user.email? For example, we'd like to use @apache.org for the email. May be, we can ask people to use project-specific configs here and use their real name and @apache.org address. Is there any downside to letting people use their global values for these configs? Moreover, do we want to use --author=Author Name em...@address.com javascript:_e(%7B%7D,'cvml','em...@address.com '); when committing on behalf of a particular contributor? Fetching the email-address is complicated here. Should we use the contributor's email from JIRA? What if that is not their @apache address? On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla ka...@cloudera.com javascript:_e(%7B%7D,'cvml','ka...@cloudera.com '); wrote: Thanks for your input, Steve. Sorry for sending the email out that late, I sent it as soon as I could. On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran ste...@hortonworks.com javascript:_e(%7B%7D,'cvml','ste...@hortonworks.com'); wrote: just caught up with this after some offlininess...15:48
Re: Updates on migration to git
Yes, we have requested for force-push disabled on trunk and branch-* branches. I didn't test it though :P, it is not writable yet. On Tue, Aug 26, 2014 at 5:48 PM, Todd Lipcon t...@cloudera.com wrote: Hey Karthik, Just to confirm, have we disabled force-push support on the repo? In my experience, especially when a project has committers new to git, force-push support causes more trouble than it's worth. -Todd On Tue, Aug 26, 2014 at 4:39 PM, Karthik Kambatla ka...@cloudera.com wrote: Looks like our git repo is good to go. On INFRA-8195, I am asking Daniel to enable writing to it. In case you find any issues, please comment on the JIRA. Thanks Karthik On Tue, Aug 26, 2014 at 3:28 PM, Arpit Agarwal aagar...@hortonworks.com wrote: I cloned the new repo, built trunk and branch-2, verified all the branches are present. Also checked a few branches and the recent commit history matches our existing repo. Everything looks good so far. On Tue, Aug 26, 2014 at 1:19 PM, Karthik Kambatla ka...@cloudera.com wrote: The git repository is now ready for inspection. I ll take a look shortly, but it would be great if a few others could too. Once we are okay with it, we can ask it to be writable. On Tuesday, August 26, 2014, Karthik Kambatla ka...@cloudera.com wrote: Hi Suresh There was one vote thread on whether to migrate to git, and the implications to the commit process for individual patches and feature branches - https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html . Prior to that, there was a discuss thread on the same topic. As INFRA handles the actual migration from subversion to git, the vote didn't include those specifics. The migration is going on as we speak (See INFRA-8195). The initial expectation was that the migration would be done in a few hours, but it has been several hours and the last I heard the import was still running. I have elaborated on the points in the vote thread and drafted up a wiki page on how-to-commit - https://wiki.apache.org/hadoop/HowToCommitWithGit . We can work on improving this further and call a vote thread on those items if need be. Thanks Karthik On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas sur...@hortonworks.com javascript:_e(%7B%7D,'cvml','sur...@hortonworks.com'); wrote: Karthik, I would like to see detailed information on how this migration will be done, how it will affect the existing project and commit process. This should be done in a document that can be reviewed instead of in an email thread on an ad-hoc basis. Was there any voting on this in PMC and should we have a vote to ensure everyone is one the same page on doing this and how to go about it? Regards, Suresh On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla ka...@cloudera.com javascript:_e(%7B%7D,'cvml','ka...@cloudera.com'); wrote: Last I heard, the import is still going on and appears closer to getting done. Thanks for your patience with the migration. I ll update you as and when there is something. Eventually, the git repo should be at the location in the wiki. On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla ka...@cloudera.com javascript:_e(%7B%7D,'cvml','ka...@cloudera.com'); wrote: Thanks for bringing these points up, Zhijie. By the way, a revised How-to-commit wiki is at: https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to make changes and improve it. On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen zs...@hortonworks.com javascript:_e(%7B%7D,'cvml','zs...@hortonworks.com'); wrote: Do we have any convention about user.name and user.email? For example, we'd like to use @apache.org for the email. May be, we can ask people to use project-specific configs here and use their real name and @apache.org address. Is there any downside to letting people use their global values for these configs? Moreover, do we want to use --author=Author Name em...@address.com javascript:_e(%7B%7D,'cvml','em...@address.com '); when committing on behalf of a particular contributor? Fetching the email-address is complicated here. Should we use the contributor's email from JIRA? What if that is not their @apache address? On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla ka...@cloudera.com javascript:_e(%7B%7D,'cvml',' ka...@cloudera.com '); wrote:
[jira] [Created] (HADOOP-11010) Post-9902 Umbrella JIRA
Allen Wittenauer created HADOOP-11010: - Summary: Post-9902 Umbrella JIRA Key: HADOOP-11010 URL: https://issues.apache.org/jira/browse/HADOOP-11010 Project: Hadoop Common Issue Type: Bug Reporter: Allen Wittenauer Umbrella JIRA to keep track of bug fixes and enhancements, now that the major portion of the shell script rewrite has been committed. -- This message was sent by Atlassian JIRA (v6.2#6252)
