[
https://issues.apache.org/jira/browse/MAPREDUCE-4933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandy Ryza resolved MAPREDUCE-4933.
---
Resolution: Fixed
> MR1 final merge asks for length of file it just wrote before flus
+1 (non-binding)
I am really glad to see this happening! As people already mentioned, this has
been a great engineering effort involving many people!
Folks raised some valid concerns below and I thought it would be good to share
my 2 cents. In my opinion, we don't have to solve all these probl
On Wed, Feb 27, 2013 at 2:54 PM, Suresh Srinivas wrote:
> With that we need to decide how our precommit process looks.
> My inclination is to wait for +1 from precommit builds on
> both the platforms to ensure no issues are introduced.
> Thoughts?
>
> 2. Feature development impact
> Some questions
[
https://issues.apache.org/jira/browse/MAPREDUCE-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe resolved MAPREDUCE-4831.
---
Resolution: Not A Problem
After discussing this at length with Bobby, we came to the conc
Thanks for raising good questions.
Currently the merge patch passes all the tests on Linux, hence
the proposal for merging the patch to trunk. But as Bobby, Harsh
and Eli pointed out, before declaring support for Windows, we need the
discussion on the following:
1. Precommit and development proce
Sandy Ryza created MAPREDUCE-5036:
-
Summary: Default shuffle handler port should not be 8080
Key: MAPREDUCE-5036
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5036
Project: Hadoop Map/Reduce
Bobby raises some good questions. A related one, since most current
developers won't add Windows support for new features that are
platform specific is it assumed that Windows development will either
lag or will people actively work on keeping Windows up with the
latest? And vice versa in case Wi
Similar personal concern as Robert: Does this bring about a
development process change? Do new features all need to work on
Windows as well to go into trunk (i.e. immediately or eventually,
either way requires a new policy for all of us devs)? Not that anyone
would be avoiding doing that, I just as
[
https://issues.apache.org/jira/browse/MAPREDUCE-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved MAPREDUCE-5035.
--
Resolution: Fixed
Fix Version/s: 1.2.0
Hadoop Flags: Reviewed
I just committed
After this is merged in is Windows still going to be a second class
citizen but happens to work for more than just development or is it a
fully supported platform where if something breaks it can block a release?
How do we as a community intend to keep Windows support from breaking?
We don't have
Tom White created MAPREDUCE-5035:
Summary: Update MR1 memory configuration docs
Key: MAPREDUCE-5035
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5035
Project: Hadoop Map/Reduce
Issue
11 matches
Mail list logo
