sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mengwei Ding (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SQOOP-1099) Sqoop2: Missing hadoop jar exceptions should be logged in sqoop.log
Date Tue, 02 Jul 2013 23:10:20 GMT

     [ https://issues.apache.org/jira/browse/SQOOP-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mengwei Ding resolved SQOOP-1099.
---------------------------------

    Resolution: Won't Fix

Missing hadoop jar would result in NoClassDefFoundError exception, which would be throw out
by the Tomcat server itself. However, the sqoop.log is configured for the sqoop servlet webapp
itself. The Tomcat and one single webapp use different logging APIs.

Even if its possible to make the Tomcat server and webapp share the same logging configuration
file and output logs to the same file, it's impossible to load logging configuration at the
runtime for the Tomecat server.
                
> Sqoop2: Missing hadoop jar exceptions should be logged in sqoop.log
> -------------------------------------------------------------------
>
>                 Key: SQOOP-1099
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1099
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.99.2
>            Reporter: Abraham Elmahrek
>            Assignee: Mengwei Ding
>
> They are currently logged in server/logs/localhost-<date>.log

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message