Skip to content

Convert null message to empty string in DLQ to avoid NPE#5975

Merged
dlvenable merged 1 commit into
opensearch-project:mainfrom
JonahCalvo:NPE-dlq-fix
Aug 11, 2025
Merged

Convert null message to empty string in DLQ to avoid NPE#5975
dlvenable merged 1 commit into
opensearch-project:mainfrom
JonahCalvo:NPE-dlq-fix

Conversation

@JonahCalvo
Copy link
Copy Markdown
Contributor

Description

Currently, writing to a DLQ with an empty message leads to an error as seen in #5974. Ideally we find out the cause of this missing data, but writing with an empty message is better than having pipeline worker crash

Issues Resolved

Resolves #5974

Check List

  • New functionality includes testing.
  • New functionality has a documentation issue. Please link to it in this PR.
    • New functionality has javadoc added
  • Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: Jonah Calvo <caljonah@amazon.com>
@dlvenable dlvenable merged commit 782fae1 into opensearch-project:main Aug 11, 2025
66 of 68 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] DLQ fails to write when error message is null?

3 participants