You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a kafka pubsub subscription includes a dead letter topic, the publish to the DLT should include both the record (partition) key and value.
This is important because it's needed to support proper partitioning of the DLT as well as because some kafka consumers need the record key as well as the value for processing (ref. #2213).
Actual Behavior
Publishes to the DLT drop the record key and publish only the record value (with a null key).
Steps to Reproduce the Problem
Deploy a kafka pubsub component and a corresponding pubsub subscription component that specifies a DLT
Have the subscription endpoint return RETRY
Publish a record with key and value to the original kafka topic
Inspect the record published to the DLT and notice key is null
Release Note
RELEASE NOTE: FIX Kafka pubsub propagates partition key to DLT
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.
Expected Behavior
When a kafka pubsub subscription includes a dead letter topic, the publish to the DLT should include both the record (partition) key and value.
This is important because it's needed to support proper partitioning of the DLT as well as because some kafka consumers need the record key as well as the value for processing (ref. #2213).
Actual Behavior
Publishes to the DLT drop the record key and publish only the record value (with a null key).
Steps to Reproduce the Problem
Release Note
RELEASE NOTE: FIX Kafka pubsub propagates partition key to DLT
The text was updated successfully, but these errors were encountered: