As someone who doesn't really contribute, just lurks, I could well be
misinformed or under-informed, but I don't see why we can't deprecate a
method which could cause dangerous side effects?
People can still use the deprecated methods for backwards compatibility,
but are discouraged by compiler war
I could be missing something, but couldn't you just deprecate isSplitable
(spelled incorrectly) and create a new isSplittable as described?
On Thu, May 29, 2014 at 10:34 AM, Steve Loughran
wrote:
> On 28 May 2014 20:50, Niels Basjes wrote:
>
> > Hi,
> >
> > Last week I ran into this problem ag
I'm thoroughly confused about which API is the recent one, which is the old
one and which method I should be using to write MapReduce applications.
I'm under the impression that MRv2 is primarily driven by the
org.apache.hadoop.mapreduce.* packages and MRv1 is primarily driven by the
org.apache.ha
You could run:
mvn install -DskipTests if you are just looking to build it, and don't care
about the tests?
On Tue, Sep 3, 2013 at 2:46 AM, John Chilton wrote:
> Hi all, I am trying to set up a new development environment on a Mac (OS X
> 10.8.4).
>
> I have checked out the source using NetBean
