Todd Lipcon created MAPREDUCE-6055:
--
Summary: native-task: findbugs, interface annotations, and other
misc cleanup
Key: MAPREDUCE-6055
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6055
Projec
Todd Lipcon created MAPREDUCE-6054:
--
Summary: native-task: speed up test runs
Key: MAPREDUCE-6054
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6054
Project: Hadoop Map/Reduce
Issue T
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 wrote:
> Hey Karthik,
>
> Just to confirm, have we disabled force-push support on the repo?
>
> In my experience, espec
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
wrote:
> Looks like our git re
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
wrote:
> I cloned the new repo, built trunk and branch-2, verified all the b
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
wrote:
> The git repository is now ready f
:) 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,
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 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
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
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-githu
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
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 wrote:
> Hi Suresh
>
> There was one vote thread on whether to migrate
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 INFR
Hi all,
I wanted to give a quick status update on the MAPREDUCE-2841 feature branch
which was started earlier this summer.
Since establishing the branch, we've accomplished a number of key items:
- Imported the initial code from github
- Made integrations with other projects more pluggable using
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
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
wrote:
>
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1875/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 35725 lines...]
Tests run: 1, Failures: 0, Errors: 0
Paul Vasilev created MAPREDUCE-6053:
---
Summary: New hadoop API don't allow dynamic key-based names for
output files
Key: MAPREDUCE-6053
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6053
Proje
17 matches
Mail list logo
