![]() | 1 | initial version |
There was an outstanding issue with the Jdbc Query Origin when running in incremental mode -- SDC-7603. This issue causes the problem you're seeing.
As you identified, the current behavior requires at least one record to be processed, then the "no-more-data" event will be trigged when no more records are available. The new behavior will be to trigger "no-more-data" event even if no records were processed by the query.
In non-incremental mode, this was not a problem.
SDC-7603 is resolved and is available in the 3.0.0.0-SNAPSHOT code line, and will be back ported to the latest builds of 2.7.2.1.