pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohini Palaniswamy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PIG-5298) Verify if org.mortbay.jetty is removable
Date Fri, 15 Sep 2017 16:55:00 GMT

    [ https://issues.apache.org/jira/browse/PIG-5298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168173#comment-16168173

Rohini Palaniswamy commented on PIG-5298:

bq. the logical thing to do IMHO would be to use just glassfish EL
  Sounds good. We have been moving away from tomcat in most hadoop projects (For eg: Oozie).
Jetty has kind of become the standard in all hadoop projects. So better to stick to it or
what it uses as we would get to know quickly if there are any security issues. 

> Verify if org.mortbay.jetty is removable
> ----------------------------------------
>                 Key: PIG-5298
>                 URL: https://issues.apache.org/jira/browse/PIG-5298
>             Project: Pig
>          Issue Type: Improvement
>    Affects Versions: 0.17.0
>            Reporter: Adam Szita
>            Assignee: Nandor Kollar
>         Attachments: PIG-5298_1.patch
> Although we pull in jetty libraries in ivy Pig does not depend on org.mortbay.jetty explicitly.
The only exception I see is in Piggybank where I think this can be swapped by javax.el-api
and log4j.
> We should investigate (check build, run unit tests across all exec modes) and remove
if it turns out to be unnecessary.

This message was sent by Atlassian JIRA

View raw message