https://community.cloudera.com/t5/Support-Questions/Convert-sqoop-job-upper-bound-and-lower-bound-values-to/m-p/122470#M85226 <P>I should also note that the desired output appears if I use --table instead of --query, however --query is neccersary in order to tidy up the data.</P> Fri, 11 Mar 2016 23:47:30 GMT daniel_perry 2016-03-11T23:47:30Z https://community.cloudera.com/t5/Support-Questions/Convert-sqoop-job-upper-bound-and-lower-bound-values-to/m-p/122469#M85225 <P>I'm having an issue I was hoping someone could help me with. I'll try and explain as best as I can.</P><P>I'm currently trying to run an incremental sqoop job which pulls new data down based on when the job was last run. To do this I have used the incremental append option. This sqoop job also contains a free form query which is used to clean up columns containing additional whitespaces etc. The problem I am having is that I am doing the incremental import based on a timestamp column and the lower bound and upper bound values being generated by the sqoop job are not of a timestamp value so I am recieving type errors whenever I try and run the job. My question is, is there a way to insert a to_timestamp function around the lower bound and upper bound values so that the values are in the correct format when they are comparred to the timestamp column? </P><P>Some example code below:</P><P>Current output</P><PRE>WHERE ts &gt; '2014-08-10 10:09:36.094' AND ts &lt;= '2016-03-05 10:09:36.094'</PRE><P>Desired output</P><PRE>WHERE ( ts &gt; TO_TIMESTAMP('2014-08-10 10:09:36.094', 'YYYY-MM-DD HH24:MI:SS.FF') AND ts &lt;= TO_TIMESTAMP('2016-03-05 10:09:36.094', 'YYYY-MM-DD HH24:MI:SS.FF') )</PRE> Fri, 11 Mar 2016 22:43:04 GMT https://community.cloudera.com/t5/Support-Questions/Convert-sqoop-job-upper-bound-and-lower-bound-values-to/m-p/122469#M85225 daniel_perry 2016-03-11T22:43:04Z https://community.cloudera.com/t5/Support-Questions/Convert-sqoop-job-upper-bound-and-lower-bound-values-to/m-p/122470#M85226 <P>I should also note that the desired output appears if I use --table instead of --query, however --query is neccersary in order to tidy up the data.</P> Fri, 11 Mar 2016 23:47:30 GMT https://community.cloudera.com/t5/Support-Questions/Convert-sqoop-job-upper-bound-and-lower-bound-values-to/m-p/122470#M85226 daniel_perry 2016-03-11T23:47:30Z https://community.cloudera.com/t5/Support-Questions/Convert-sqoop-job-upper-bound-and-lower-bound-values-to/m-p/122471#M85227 <P>I've resolved this issue, turned out the problem came from a driver that was being used</P><P>--driver oracle.jdbc.OracleDriver</P><P>Removed the driver, problem solved!</P> Sat, 12 Mar 2016 00:16:55 GMT https://community.cloudera.com/t5/Support-Questions/Convert-sqoop-job-upper-bound-and-lower-bound-values-to/m-p/122471#M85227 daniel_perry 2016-03-12T00:16:55Z