paste the error log for your reference: 2017-01-10 17:45:19,443 INFO [org.apache.sqoop.connector.jdbc.GenericJdbcFromInitializer.configurePartitionProperties(GenericJdbcFromInitializer.java:152)] Using partition column: id 2017-01-10 17:45:19,443 INFO [org.apache.sqoop.connector.jdbc.GenericJdbcFromInitializer.configurePartitionProperties(GenericJdbcFromInitializer.java:181)] Incremental new max value query: SELECT *MAX(``)* FROM `table`.`test_table` 2017-01-10 17:45:19,449 ERROR [org.apache.sqoop.server.SqoopProtocolServlet.doPut(SqoopProtocolServlet.java:86)] Exception in PUT http://localhost:12000/sqoop/v1/job/vcg_bi_a_account_contact_job/start org.apache.sqoop.common.SqoopException: GENERIC_JDBC_CONNECTOR_0016:Can't fetch schema at org.apache.sqoop.connector.jdbc.GenericJdbcFromInitializer.initialize(GenericJdbcFromInitializer.java:64) at org.apache.sqoop.connector.jdbc.GenericJdbcFromInitializer.initialize(GenericJdbcFromInitializer.java:47)
On Tue, Jan 10, 2017 at 6:33 PM, wenxing zheng <wenxing.zh...@gmail.com> wrote: > Dear gurus, > > I am using the Sqoop2 REST API to update the job for below items with NULL. > > "incrementalRead.checkColumn": null, "incrementalRead.lastValue": null > > But after the update, I found the checkColumn is still in "", and when I > started the job, it failed to start due to "checkColumn" is not null, but > in "". > > My questions are: > 1. How to update the the checkColumn with null to avoid the checking on > the checkColumn? > 2. If the checkColumn is being set, but if the source table's checkColumn > are all in NULL, the job will fail to. Can we support such case? > > Thanks, Wenxing >
