sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SQOOP-522) Move printing error "ERROR orm.CompilationManager: Could not rename" to DEBUG
Date Tue, 24 Jul 2012 14:35:35 GMT
Jarek Jarcec Cecho created SQOOP-522:

             Summary: Move  printing error "ERROR orm.CompilationManager: Could not rename"
                 Key: SQOOP-522
                 URL: https://issues.apache.org/jira/browse/SQOOP-522
             Project: Sqoop
          Issue Type: Improvement
            Reporter: Jarek Jarcec Cecho
            Assignee: Jarek Jarcec Cecho
            Priority: Minor
             Fix For: 1.4.2

We're currently creating generated class in temporary directory and then moving to final directory.
However in case that the file is already there (for example from previous run), we print out
ogly exception stack trace. I would like to change this error message from ERROR to DEBUG
as this error message is being ignored anyway.

Example of the stack trace:

12/04/09 17:28:38 ERROR orm.CompilationManager: Could not rename /tmp/location to /final/location
java.io.IOException: Destination '/final/location' already exists 
at org.apache.commons.io.FileUtils.moveFile(FileUtils.java:1811) 
at org.apache.sqoop.orm.CompilationManager.compile(CompilationManager.java:227) 
at org.apache.sqoop.tool.CodeGenTool.generateORM(CodeGenTool.java:83)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message