Event Generation

The Google Cloud Storage origin can generate events when it completes processing all available data and the configured batch wait time has elapsed.

Google Cloud Storage events can be used in any logical way. For example:

With the Google Cloud Storage executor to perform tasks after writing an object or whole file.
With the Pipeline Finisher executor to stop the pipeline and transition the pipeline to a Finished state when the origin completes processing available data.
When you restart a pipeline stopped by the Pipeline Finisher executor, the origin continues processing from the last-saved offset unless you reset the origin.
For an example, see Stopping a Pipeline After Processing All Available Data.
With a destination to store event information.
For an example, see Preserving an Audit Trail of Events.

For more information about dataflow triggers and the event framework, see Dataflow Triggers Overview.