[
https://issues.apache.org/jira/browse/SQOOP-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706476#comment-13706476
]
Hudson commented on SQOOP-1130:
-------------------------------
Integrated in Sqoop2-hadoop100 #482 (See
[https://builds.apache.org/job/Sqoop2-hadoop100/482/])
SQOOP-1130: Sqoop2: Sqoop MapReduce Job Failed when max and min boundary
are both null (Revision a3abffcd591f16a5f4f47fa43eeef7dcdec68cf7)
Result = SUCCESS
jarcec :
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=a3abffcd591f16a5f4f47fa43eeef7dcdec68cf7
Files :
*
connector/connector-generic-jdbc/src/main/java/org/apache/sqoop/connector/jdbc/GenericJdbcImportPartitioner.java
> Sqoop2: Sqoop MapReduce Job Failed when max and min boundary are both null
> --------------------------------------------------------------------------
>
> Key: SQOOP-1130
> URL: https://issues.apache.org/jira/browse/SQOOP-1130
> Project: Sqoop
> Issue Type: Bug
> Components: connectors/generic
> Affects Versions: 1.99.2
> Environment: Mysql import data to HDFS
> Reporter: Mengwei Ding
> Assignee: Mengwei Ding
> Fix For: 1.99.3
>
> Attachments: SQOOP-1130.1.patch
>
>
> It happens that all the values in the partition column are null. In this
> case, when Sqoop is partitioning data, it will find the max and min boundary
> are both null. Sqoop handles this case, but there is a bug.
> Currently, the Map task throw the following exception in this case:
> {code}
> org.apache.sqoop.common.SqoopException: MAPRED_EXEC_0017:Error occurs during
> extractor run
> at org.apache.sqoop.job.mr.SqoopMapper.run(SqoopMapper.java:94)
> at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:672)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:330)
> at org.apache.hadoop.mapred.Child$4.run(Child.java:268)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:396)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1408)
> at org.apache.hadoop.mapred.Child.main(Child.java:262)
> Caused by: org.apache.sqoop.common.SqoopException:
> GENERIC_JDBC_CONNECTOR_0002:Unable to execute the SQL statement
> at
> org.apache.sqoop.connector.jdbc.GenericJdbcExecutor.executeQuery(GenericJdbcExecutor.java:59)
> at
> org.apache.sqoop.connector.jdbc.GenericJdbcImportExtractor.extract(GenericJdbcImportExtractor.java:51)
> at
> org.apache.sqoop.connector.jdbc.GenericJdbcImportExtractor.extract(GenericJdbcImportExtractor.java:31)
> at org.apache.sqoop.job.mr.SqoopMapper.run(SqoopMapper.java:89)
> ... 7 more
> Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You
> have an error in your SQL syntax; check the manual that corresponds to your
> MySQL server version for the right syntax to use near 'NULL' at line 1
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
> at com.mysql.jdbc.Util.getInstance(Util.java:386)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1054)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4187)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4119)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2570)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2731)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2809)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2758)
> at com.mysql.jdbc.StatementImpl.executeQuery(StatementImpl.java:1612)
> at
> org.apache.sqoop.connector.jdbc.GenericJdbcExecutor.executeQuery(GenericJdbcExecutor.java:56)
> ... 10 more
> {code}
--
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
