Owen, Doug, Tom
Could you please formulate and reply to this email separately
what would be an *ACCEPTABLE *resolution of
HADOOP-6685 for *YOU *to move *0.22* forward.
Just trying to get something to work with to get us beyond the stagnation
point.
It could be I want this patch in/out
On 12/17/2010 02:34 PM, Konstantin Shvachko wrote:
It could be a zero-option plan - remove dependencies both for Avro and
ProtocolBuffers out into libraries, similar to schedulers.
I'd be fine with removing Avro from the mapreduce user's classpath.
It's currently an unused option for RPC, and
So, with test-patch updated to show the failing tests, saving the
developers the need to go and verify that the failed tests are all
known, how do people feel about turning on test-patch again for HDFS
and mapred? I think it'll help prevent any more tests from entering
the yeah, we know category.
+1, thanks for doing this.
On Fri, Dec 17, 2010 at 3:19 PM, Jakob Homan jgho...@gmail.com wrote:
So, with test-patch updated to show the failing tests, saving the
developers the need to go and verify that the failed tests are all
known, how do people feel about turning on test-patch again for
Considering that because of these 4 faulty cases every patch will be
-1'ed a patch author will still have to look at it and make a comment
why this particular -1 isn't valid. Lesser work, perhaps, but messier
IMO. I'm not blocking it - I just feel like there's a better way.
--
Take care,
On Fri, Dec 17, 2010 at 3:55 PM, Jakob Homan jgho...@gmail.com wrote:
If HDFS is added to the test-patch queue right now we get
nothing but dozens of -1'ed patches.
There aren't dozens of patches being submitted currently. The -1
isn't the important thing, it's the grunt work of actually
I agree with Cos on fixing HDFS-1511 first. Once that is done I'll enable hdfs
patch testing.
Cheers,
Nige
Sent from my iPhone4
On Dec 17, 2010, at 7:01 PM, Konstantin Boudnik c...@apache.org wrote:
One more issue needs to be addressed before test-patch is turned on HDFS is
