hi @Mahesh Assuming that you have JDBC Multitable consumer Origin, since you are reading from multiple table.
You can leverage the event record no-more-data generated by JDBC Multitable Consumer origin. ref : here
sdc.event.type | Event type. Uses the following type: - no-more-data - Generated when the origin completes processing all data returned by the queries for all tables.
- schema-finished - Generated when the origin completes processing all rows within a schema.
- table-finished - Generated when the origin completes processing all rows within a table.
|
With the help of event stream you can stop a pipeline after processing all available data.
more detailed can be found here
https://docs.streamsets.com/portal/platform-datacollector/latest/datacollector/UserGuide/Solutions/StopPipeline.html#concept_kff_ykv_lz
And have scheduler configured in control hub to trigger this job periodically
https://docs.streamsets.com/portal/platform-controlhub/controlhub/UserGuide/Scheduler/ScheduledTasks_Creating.html#task_y5k_f1g_ndb
what if i’m using rest api calls to get data. how to know whether the server is empty? does the above solution works for this case too?
In Rest api , you can configure for the error code 400 , in this case it will throw error message which signifies no. more data in api.