You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Greg Wilkins (JIRA)" <ji...@apache.org> on 2008/10/15 05:54:46 UTC

[jira] Commented: (HADOOP-1650) Upgrade Jetty to 6.x

    [ https://issues.apache.org/jira/browse/HADOOP-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639708#action_12639708 ] 

Greg Wilkins commented on HADOOP-1650:
--------------------------------------

Hi, I'm the lead developer on Jetty and would be happy to help out with optimizing jetty-6 for hadoop.
I'm watching this issue, so just comment if you want my help.
 

> Upgrade Jetty to 6.x
> --------------------
>
>                 Key: HADOOP-1650
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1650
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>         Attachments: 1650-20080120.patch, 1650-jetty6.1.9.patch, 1650-jetty6.1.9.v1.patch, hadoop-1650-jetty6.1.5.patch, hadoop-jetty6.1.4-lib.tar.gz, hadoop-jetty6.1.6-lib.tar.gz, hadoop-jetty6.1.9-lib.tar.gz, jetty-hadoop-6.1.6.patch, jetty-hbase.patch, jetty6.1.4.patch, jetty6.1.6.patch
>
>
> This is the third attempt at moving to jetty6. Apparently, the jetty-6.1.4 has fixed some of the issues we discovered in jetty during HADOOP-736 and HADOOP-1273. I'd like to keep this issue open for sometime so that we have enough time to test out things.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.