Hi Jarek, Do you know what log file I’d find that in? It’s not in the job log nor the task tracker’s setup/map/cleanup logs.
-- Best wishes, Dave Cardwell. http://davecardwell.co.uk/ On 4 April 2013 15:56, Jarek Jarcec Cecho <[email protected]> wrote: > Hi Dave, > do you think that you can share entire stack trace of the exception? I > think that I do know where the issue might be, but I would like to verify > that. > > However please do note that Sqoop is not general query tool and using it > for calling stored procedures is not supported nor recommended use. The > tool "eval" is available only for evaluation purpose and should not be used > in any production workflow. > > Jarcec > > On Thu, Apr 04, 2013 at 02:28:55PM +0100, Dave Cardwell wrote: > > I have a Sqoop action which uses sqoop-eval to call a MySQL stored > > procedure. It works fine from the command line, and the call actually > > completes in Oozie giving an external status of “SUCCEEDED”, but the > > resulting status of the action is ERROR, with the following message: > > > > IllegalArgumentException: JobId string : is not properly formed > > > > Here is the action configuration: > > > > <sqoop xmlns="uri:oozie:sqoop-action:0.2"> > > <job-tracker>my.server.com:8021</job-tracker> > > <name-node>hdfs://my.server.com:8020</name-node> > > <arg>eval</arg> > > <arg>--query</arg> > > <arg>CALL `move_cdrs_to_working`;</arg> > > <arg>--connect</arg> > > <arg>jdbc:mysql://my.server.com/my_database</arg> > > <arg>--username</arg> > > <arg>my_user</arg> > > <arg>--password</arg> > > <arg>my_password</arg> > > </sqoop> > > > > > > The job log: > > https://gist.github.com/davecardwell/fd08802d6bdfd901d38a > > > > > > Any ideas? > > > > -- > > Best wishes, > > Dave Cardwell. > > > > http://davecardwell.co.uk/ >
