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
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
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:
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
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
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
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
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
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
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
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:
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
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
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:
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
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
[
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
:) 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
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
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
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
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:
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
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
24 matches
Mail list logo
