[
https://issues.apache.org/jira/browse/SQOOP-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238970#comment-14238970
]
Veena Basavaraj edited comment on SQOOP-1862 at 12/9/14 4:42 AM:
-----------------------------------------------------------------
Looks like the HDFS is probably not giving the date in expected CSV format, ...
so hdfs does setText, so this mean it shoudl encode dates in quotes .. etc
etc...
The more grave situation is that both jdbc and hdfs lack unit tests on how they
write their data, I have added a ticket for jdbc connector
https://issues.apache.org/jira/browse/SQOOP-1835, while fixing
https://issues.apache.org/jira/browse/SQOOP-1830, but hdfs needs similar tests
was (Author: vybs):
Looks like the HDFS is probably not giving the date in expected CSV format, ...
so hdfs does setText, so this mean it shoudl encode dates in quotes .. etc
etc...
> Sqoop2: Unable to export data to jdbc database
> ----------------------------------------------
>
> Key: SQOOP-1862
> URL: https://issues.apache.org/jira/browse/SQOOP-1862
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.5
> Reporter: Qian Xu
>
> I did a round-trip data import test with unexpected results.
> 1. I used JdbcConnector as FROM and HdfsConnector as TO. Data was written
> onto HDFS expectedly.
> 2. I used HdfsConnector as FROm and JdbcConnector as TO. Data is expected to
> be written into an empty mysql table. Schema is exactly the same as it is in
> step 1.
> Now the progress is blocked at 0%. Here is the error message:
> {code}
> 2014-12-09 12:17:23,653 ERROR [OutputFormatLoader-consumer]
> org.apache.sqoop.job.mr.SqoopOutputFormatLoadExecutor: Error while loading
> data out of MR job.
> org.apache.sqoop.common.SqoopException: GENERIC_JDBC_CONNECTOR_0002:Unable to
> execute the SQL statement
> at
> org.apache.sqoop.connector.jdbc.GenericJdbcExecutor.executeBatch(GenericJdbcExecutor.java:189)
> at
> org.apache.sqoop.connector.jdbc.GenericJdbcLoader.load(GenericJdbcLoader.java:58)
> at
> org.apache.sqoop.connector.jdbc.GenericJdbcLoader.load(GenericJdbcLoader.java:25)
> at
> org.apache.sqoop.job.mr.SqoopOutputFormatLoadExecutor$ConsumerThread.run(SqoopOutputFormatLoadExecutor.java:249)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.sql.BatchUpdateException: Data truncation: Incorrect date
> value: '’' for column 'date' at row 1
> at
> com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:1981)
> at
> com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1388)
> at
> org.apache.sqoop.connector.jdbc.GenericJdbcExecutor.executeBatch(GenericJdbcExecutor.java:183)
> ... 8 more
> Caused by: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect
> date value: '’' for column 'date' at row 1
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4224)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4158)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2615)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2776)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2840)
> at
> com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2082)
> at
> com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2334)
> at
> com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:1933)
> ... 10 more
> {code}
> The date type of the column is "DATE". Dumped context looks like
> "20014-12-08".
> It seems the field value is not correct. "’" stands for ascii code 170 and
> 161.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
