Stream processing operations

From release v1.4.0 onwards, you can start and stop the stream processing using the API and the web interface. This is a convenient feature that lets you stop the ingestion in case of a configuration error. This is convenient, because having an erroneous configurations might result in the messages being rejected and sent to the dead-letter queue (which might take more manual effort to replay them back), or erroneously parsed messaged persisted in tables (which will need manual seek and removal).

The API provides the following functionalities:

• Start the ingestion.
• Stop the ingestion.
• Getting the status of the ingestion.

Note: Stopping or starting the ingestion impacts all of the services involved in all the processing pipelines. All of the processing metrics in the monitoring dashboard will indicate that they are stopped, and the internal queues depth won't change.