Add pipeline DLQ support for rds source#6817
Merged
oeyh merged 4 commits intoopensearch-project:mainfrom May 7, 2026
Merged
Conversation
Signed-off-by: Hai Yan <oeyh@amazon.com>
Signed-off-by: Hai Yan <oeyh@amazon.com>
Signed-off-by: Hai Yan <oeyh@amazon.com>
b2c7aed to
108da49
Compare
divbok
previously approved these changes
May 6, 2026
…gured Signed-off-by: Hai Yan <oeyh@amazon.com>
divbok
approved these changes
May 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds pipeline DLQ support to the RDS source plugin for both the stream path (binlog/WAL) and the export path.
When a
dlq_pipelineis configured, failed events are sent to it with_failure_metadatacontainingpluginId,pluginName,pipelineName, anderrorMessage.Stream path (BinlogEventListener / LogicalReplicationEventProcessor):
Export path (DataFileLoader):
When no
dlq_pipelineis configured, behavior is unchanged — errors are logged and counters incremented.Testing
Tested end-to-end locally against Aurora MySQL with a
dlq_pipelineconfigured with a stdout sink.Stream path:
_failure_metadataExport path:
_failure_metadataNo DLQ configured:
dlq_pipelineis defined,failurePipelineis null andsendToFailurePipelinereturns immediately with no side effectsIssues Resolved
N/A
Check List