[DBZ-1583] Propagate replicator exception so failure reason is available from Connect - Red Hat Issue Tracker

XML

Word

Printable

Details

Type: Enhancement
Status: Closed (View Workflow)
Priority: Minor
Resolution: Done
Affects Version/s: 1.0.0.Beta2
Fix Version/s: 1.0.0.Beta3
Component/s: mongodb-connector
Labels:
None

Git Pull Request:
https://github.com/debezium/debezium/pull/1110

Description

It would be helpful for users to propagate the Replicator failure so that the /status endpoint can report the failure reason rather than having to force users to examine the connector logs themselves to determine the reason for failure.

Attachments

Activity

People

Assignee:: Chris Cranford

Reporter:: Chris Cranford

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2019/Oct/29 11:09 AM

Updated:: 2019/Nov/14 3:28 AM

Resolved:: 2019/Oct/29 11:17 AM