Skip to content

[1.18] pubsub/kafka: per message partitioning#5078

Open
JoshVanL wants to merge 2 commits intodapr:v1.18from
JoshVanL:kafka-per-msg-partition
Open

[1.18] pubsub/kafka: per message partitioning#5078
JoshVanL wants to merge 2 commits intodapr:v1.18from
JoshVanL:kafka-per-msg-partition

Conversation

@JoshVanL
Copy link
Contributor

Document the new partitionNumber per-call metadata field, including usage example, precedence rules over partitionKey, and valid values.

Implemented in dapr/components-contrib#4298

Document the new partitionNumber per-call metadata field, including
usage example, precedence rules over partitionKey, and valid values.

Implemented in dapr/components-contrib#4298

Signed-off-by: joshvanl <me@joshvanl.dev>
Copilot AI review requested due to automatic review settings March 19, 2026 12:21
@JoshVanL JoshVanL requested review from a team as code owners March 19, 2026 12:21
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Kafka pub/sub component documentation to describe the newly supported per-message partitioning option (partitionNumber) when publishing events via Dapr.

Changes:

  • Added documentation for metadata.partitionNumber, including an example and precedence over partitionKey.
  • Updated the “Message headers” section to exclude partitionNumber from metadata forwarded as Kafka headers.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

@JoshVanL JoshVanL changed the title pubsub/kafka: per message partitioning [1.18] pubsub/kafka: per message partitioning Mar 19, 2026
Signed-off-by: joshvanl <me@joshvanl.dev>
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.

2 participants