sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Ma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-910) Sqoop2: Move to embedded jetty from tomcat
Date Wed, 09 Sep 2015 05:44:45 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736224#comment-14736224
] 

Colin Ma commented on SQOOP-910:
--------------------------------

Hi, [~jarcec], the goal for this ticket is using Jetty instead of Tomcat with Sqoop2, not
only in integration test. I think the following things should be done:
1. update sqoop-server, package with jar and not with war.
2. Create new class for Jetty server and update the start script(sqoop.sh).
3. Update test case using Jetty instead of tomcat.
4. Update package script, don't package tomcat related.
5. Clear the source code, remove tomcat related.

Is there anything I missed?
Because these items can't be committed one by one, do you think it's reasonable to create
sub-tasks for these items and commit them all at last?

> Sqoop2: Move to embedded jetty from tomcat
> ------------------------------------------
>
>                 Key: SQOOP-910
>                 URL: https://issues.apache.org/jira/browse/SQOOP-910
>             Project: Sqoop
>          Issue Type: Bug
>          Components: sqoop2-server
>    Affects Versions: 1.99.1
>            Reporter: Hari Shreedharan
>            Assignee: Colin Ma
>             Fix For: 2.0.0
>
>
> Embedded jetty makes it much easier to configure and replace the current jar with the
new one - in testing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message