You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by pi song <pi...@gmail.com> on 2008/06/06 13:40:22 UTC

Slow unit testing and Jetty

Regarding slow unit testing issue before, somebody has sent me an email
claiming he also has the same problem. He has identified the problem which
seems to be a bug in Jetty.  One possible way to fix this is to fix directly
in the Jetty source code (The current Jetty that we use is not the latest
major version so I'm not sure if they still support it).

This seems to be a bit difficult because Jetty is embedded in Hadoop and
Hadoop is used in Pig.  Technically we should we able to patch the Jetty
source code (at least for our own), recompile with Hadoop. Is there any
licensing issue associated with this at all?

Pi

PS. I have to test the fix again to make sure that it really solves the
problem. At this stage I'm just curious about how this process works.

RE: Slow unit testing and Jetty

Posted by Olga Natkovich <ol...@yahoo-inc.com>.
Pi,

I asked Hadoop QA to verify this theory. Here is the response I got: The
jetty-5.1.4.jar in Hadoop hasn't been touched since November.

Olga 

> -----Original Message-----
> From: pi song [mailto:pi.songs@gmail.com] 
> Sent: Friday, June 06, 2008 4:40 AM
> To: pig-dev@incubator.apache.org
> Subject: Slow unit testing and Jetty
> 
> Regarding slow unit testing issue before, somebody has sent 
> me an email claiming he also has the same problem. He has 
> identified the problem which seems to be a bug in Jetty.  One 
> possible way to fix this is to fix directly in the Jetty 
> source code (The current Jetty that we use is not the latest 
> major version so I'm not sure if they still support it).
> 
> This seems to be a bit difficult because Jetty is embedded in 
> Hadoop and Hadoop is used in Pig.  Technically we should we 
> able to patch the Jetty source code (at least for our own), 
> recompile with Hadoop. Is there any licensing issue 
> associated with this at all?
> 
> Pi
> 
> PS. I have to test the fix again to make sure that it really 
> solves the problem. At this stage I'm just curious about how 
> this process works.
>