Description
The Sqoop action currently assumes that it will always launch an MR job, so if it doesn't (which happens when eval is used), then even if the actual action succeeds, Oozie will run into an IllegalArgumentException trying to parse an empty string as a Hadoop job id. The error is mentioned in the Oozie log, but there is no stack trace.
You get this confusing output when querying for the action:
oozie job -info 0000002-130710121740870-oozie-oozi-W@eval ID : 0000002-130710121740870-oozie-oozi-W@eval ------------------------------------------------------------------------------------------------------------------------------------ Console URL : http://localhost:50030/jobdetails.jsp?jobid=job_201306132134_0027 Error Code : IllegalArgumentException Error Message : IllegalArgumentException: JobId string : is not properly formed External ID : job_201306132134_0027 External Status : SUCCEEDED Name : eval Retries : 0 Tracker URI : localhost:8021 Type : sqoop Started : 2013-07-10 19:29 GMT Status : ERROR Ended : - ------------------------------------------------------------------------------------------------------------------------------------
Attachments
Attachments
Issue Links
- is broken by
-
OOZIE-1012 Sqoop jobs are unable to utilize Hadoop Counters
- Closed