Documentation Home | Common Home
These steps offer various tools for manipulating the flow of a Pipeline.
This step provides a mechanism for determining whether to perform a retry or to stop in the form of a branch step. The pipeline will need to define a unique name for the counter and the maximum number of retries. The information will be tracked in the globals. This step is not a replacement for the step retries which provide a mechanism for retrying a single step when an exception occurs.
- counterName - The name of the counter to use for tracking.
- maxRetries - The maximum number of retries allowed.
- retry - This branch is used to transition to the step that needs to be retried.
- stop - This branch is used to call the step when retries have been exhausted.
This step provides a mechanism to monitor a streaming query in a pipeline. This step can safely be called without providing the streaming query and the stop action will be taken. The StreamingQueryMonitor framework provides an integration point for controlling how this step handles the streaming query.
- query - The streaming query to monitor.
- streamingMonitorClassName - Fully qualified classname of the monitor class. The default monitor class never stops the query.
- continue - This branch is used to allow restarting the streaming query.
- stop - This branch is used to call the step when streaming should not continue.