What steps will reproduce the problem?
1. Create a job spec using an operator with a descriptor that defines
inputArity=1
2. Do not attach any input to that operator
3. The job will fail silently and hang
Expected Behavior == Exception propagated to client and logged at cluster.
Version/OS == 0.2.0 on Java 7
In my case the operator in question was supposed to have inputArity=0, but
didn't due to a typo in my code.
** A null-pointer exception occurred at
edu.uci.ics.hyracks.api.job.JobSpecification:150 because opInputMap was empty.
** This exception was caught at
edu.uci.ics.hyracks.control.cc.work.JobStartWork:49 and a JobCleanupWork task
was scheduled, but no exception was reported back at the client. I didn't
investigate why this failed for this exception and not others, but I suspect it
might be because this exception occurred before my client code called
edu.uci.ics.hyracks.api.client.IHyracksClientConnection#waitForCompletion(jobId)
;
Suggestions:
** Caught exceptions should be logged at
edu.uci.ics.hyracks.control.cc.work.JobStartWork:49
** A mismatch between expected number of inputs and attached inputs should be
caught by static analysis before the plan is sent to the cluster.
Original issue reported on code.google.com by nbales on 13 Jun 2012 at 9:09
Original issue reported on code.google.com by
nbaleson 13 Jun 2012 at 9:09