The Kafka inbound connector stops processing messages in case of any error. To resume message processing, the user has to redeploy the process.
Because of this behavior, even if the user manually edits the offsets for the consumer group used by the connector, the connector won't be able to recover from this situation.
Steps to Reproduce
Initialize an inbound Kafka connector
Publish a message to the topic that contains invalid JSON, or simply doesn't match the activation condition specified in the connector
Check the connector runtime logs, activity logs in the web modeler, and make sure that the consumer was stopped
Expected Behavior
The connector should retry after a certain backoff period (e.g. 30 seconds). The external consequences may lead to offsets changing, or the activation condition starting to evaluate to true, so the connector should be able to recover.
Describe the Bug
The Kafka inbound connector stops processing messages in case of any error. To resume message processing, the user has to redeploy the process.
Because of this behavior, even if the user manually edits the offsets for the consumer group used by the connector, the connector won't be able to recover from this situation.
Steps to Reproduce
Expected Behavior
The connector should retry after a certain backoff period (e.g. 30 seconds). The external consequences may lead to offsets changing, or the activation condition starting to evaluate to true, so the connector should be able to recover.
Environment