Return-Path: X-Original-To: apmail-sqoop-dev-archive@www.apache.org Delivered-To: apmail-sqoop-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2A9A418499 for ; Tue, 7 Jul 2015 00:46:05 +0000 (UTC) Received: (qmail 72535 invoked by uid 500); 7 Jul 2015 00:46:05 -0000 Delivered-To: apmail-sqoop-dev-archive@sqoop.apache.org Received: (qmail 72492 invoked by uid 500); 7 Jul 2015 00:46:05 -0000 Mailing-List: contact dev-help@sqoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sqoop.apache.org Delivered-To: mailing list dev@sqoop.apache.org Received: (qmail 72479 invoked by uid 99); 7 Jul 2015 00:46:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jul 2015 00:46:05 +0000 Date: Tue, 7 Jul 2015 00:46:04 +0000 (UTC) From: "Abraham Elmahrek (JIRA)" To: dev@sqoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SQOOP-2389) Irrelevant error printed after connection manager fails MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SQOOP-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14615992#comment-14615992 ] Abraham Elmahrek commented on SQOOP-2389: ----------------------------------------- [~qwertymaniac], I don't know how wise it is to simply call System.exit here. Why not throw an exception instead saying "cannot connect to database" or something of that nature? > Irrelevant error printed after connection manager fails > ------------------------------------------------------- > > Key: SQOOP-2389 > URL: https://issues.apache.org/jira/browse/SQOOP-2389 > Project: Sqoop > Issue Type: Bug > Components: connectors > Affects Versions: 1.4.5 > Reporter: Harsh J > Assignee: Harsh J > Priority: Minor > Attachments: SQOOP-2389.patch > > > If you run the Sqoop CLI with a bad password, for example, you would see the below 2 errors logged at end of output: > {code} > 15/06/03 13:52:51 ERROR manager.SqlManager: Error executing statement: java.sql.SQLException: Access denied for user 'root'@'localhost' (using password: YES) > java.sql.SQLException: Access denied for user 'root'@'localhost' (using password: YES) > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:998) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3835) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3771) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:870) > at com.mysql.jdbc.MysqlIO.secureAuth411(MysqlIO.java:4280) > at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1258) > at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2239) > at com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2270) > at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2069) > at com.mysql.jdbc.ConnectionImpl.(ConnectionImpl.java:794) > at com.mysql.jdbc.JDBC4Connection.(JDBC4Connection.java:44) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at com.mysql.jdbc.Util.handleNewInstance(Util.java:389) > at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:399) > at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:325) > at java.sql.DriverManager.getConnection(DriverManager.java:571) > at java.sql.DriverManager.getConnection(DriverManager.java:215) > at org.apache.sqoop.manager.SqlManager.makeConnection(SqlManager.java:880) > at org.apache.sqoop.manager.GenericJdbcManager.getConnection(GenericJdbcManager.java:52) > at org.apache.sqoop.manager.SqlManager.execute(SqlManager.java:739) > at org.apache.sqoop.manager.SqlManager.execute(SqlManager.java:762) > at org.apache.sqoop.manager.SqlManager.getColumnInfoForRawQuery(SqlManager.java:270) > at org.apache.sqoop.manager.SqlManager.getColumnTypesForRawQuery(SqlManager.java:241) > at org.apache.sqoop.manager.SqlManager.getColumnTypesForQuery(SqlManager.java:234) > at org.apache.sqoop.manager.ConnManager.getColumnTypes(ConnManager.java:304) > at org.apache.sqoop.orm.ClassWriter.getColumnTypes(ClassWriter.java:1833) > at org.apache.sqoop.orm.ClassWriter.generate(ClassWriter.java:1645) > at org.apache.sqoop.tool.CodeGenTool.generateORM(CodeGenTool.java:96) > at org.apache.sqoop.tool.ImportTool.importTable(ImportTool.java:478) > at org.apache.sqoop.tool.ImportTool.run(ImportTool.java:605) > at org.apache.sqoop.Sqoop.run(Sqoop.java:143) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at org.apache.sqoop.Sqoop.runSqoop(Sqoop.java:179) > at org.apache.sqoop.Sqoop.runTool(Sqoop.java:218) > at org.apache.sqoop.Sqoop.runTool(Sqoop.java:227) > at org.apache.sqoop.Sqoop.main(Sqoop.java:236) > 15/06/03 13:52:51 ERROR tool.ImportTool: Encountered IOException running import job: java.io.IOException: No columns to generate for ClassWriter > at org.apache.sqoop.orm.ClassWriter.generate(ClassWriter.java:1651) > at org.apache.sqoop.tool.CodeGenTool.generateORM(CodeGenTool.java:96) > at org.apache.sqoop.tool.ImportTool.importTable(ImportTool.java:478) > at org.apache.sqoop.tool.ImportTool.run(ImportTool.java:605) > at org.apache.sqoop.Sqoop.run(Sqoop.java:143) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at org.apache.sqoop.Sqoop.runSqoop(Sqoop.java:179) > at org.apache.sqoop.Sqoop.runTool(Sqoop.java:218) > at org.apache.sqoop.Sqoop.runTool(Sqoop.java:227) > at org.apache.sqoop.Sqoop.main(Sqoop.java:236) > {code} > The second ERROR log is irrelevant to the real cause of failure. -- This message was sent by Atlassian JIRA (v6.3.4#6332)