Commit 6752a23
committed
Handle empty record sets during exporter job init
Rarely, an exporter job will run in which no qualifying records are
fetched from Sierra. Recent changes to tasks (JobPlan implementation,
etc.) did not take this into account, leading to the error described in
issue #46. This adds a check during job initialization and logs an
appropriate message if no records were found, bypassing the code path
that raised the error.1 parent 001f209 commit 6752a23
1 file changed
Lines changed: 10 additions & 15 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
374 | 374 | | |
375 | 375 | | |
376 | 376 | | |
377 | | - | |
378 | | - | |
379 | | - | |
380 | | - | |
381 | | - | |
382 | | - | |
383 | | - | |
384 | | - | |
385 | | - | |
386 | | - | |
387 | | - | |
388 | 377 | | |
389 | 378 | | |
390 | 379 | | |
| |||
435 | 424 | | |
436 | 425 | | |
437 | 426 | | |
438 | | - | |
439 | | - | |
440 | | - | |
| 427 | + | |
| 428 | + | |
| 429 | + | |
| 430 | + | |
| 431 | + | |
| 432 | + | |
| 433 | + | |
| 434 | + | |
| 435 | + | |
441 | 436 | | |
442 | 437 | | |
443 | 438 | | |
| |||
455 | 450 | | |
456 | 451 | | |
457 | 452 | | |
458 | | - | |
| 453 | + | |
459 | 454 | | |
460 | 455 | | |
461 | 456 | | |
| |||
0 commit comments