azure-event-hubs-for-kafka
azure-event-hubs-for-kafka copied to clipboard
Published
20 hours ago •
Azure
Azure
PartitionKey is not present on EventData.PartitionKey when using Kafka Producer
Description
When consuming with an EventHub consumer, the PartitionKey from Azure.Messaging.EventHubs.EventData.PartitionKey is not present when messages are published to a Kafka-enabled EventHub using a Kafka Producer. When publishing with an EventHub publisher, the PartitionKey is present.
How to reproduce
- Create a Kafka Producer using Confluent libraries.
- Publish a single message, purposefully setting
Confluent.Kafka.Message.Keyto a string.
- Observe the PartitionKey is not present on the EventData object.
Has it worked previously?
When using EventHubs Producer, the PartitionKey is present (using Service Bus Explorer v.4.1.112)
Checklist
IMPORTANT: We will close issues where the checklist has not been completed or where adequate information has not been provided.
Please provide the relevant information for the following items:
- [x] SDK (include version info):
Confluent.Kafka 1.5.0; dotnet 3.1 - [ ] Sample you're having trouble with:
Not Available - [ ] If using Apache Kafka Java clients or a framework that uses Apache Kafka Java clients, version:
<REPLACE with e.g., 1.1.0> - [x] Kafka client configuration:
(Screenshot above) - [x] Namespace and EventHub/topic name: velocity-dev-eh-eu2/dg-test
- [x] Consumer or producer failure
Producer failure - [x] Timestamps in UTC
8/26/2020 5:43 PM - [x] group.id or client.id
$Default - [ ] Logs provided (with debug-level logging enabled if possible, e.g. log4j.rootLogger=DEBUG) or exception call stack
- [x] Standalone repro
N/A - [x] Operating system:
Windows 10 Version 10.0.19041 Build 19041 - [ ] Critical issue
If this is a question on basic functionality, please verify the following:
- [ ] Port 9093 should not be blocked by firewall ("broker cannot be found" errors)
- [ ] Pinging FQDN should return cluster DNS resolution (e.g.
$ ping namespace.servicebus.windows.netreturns ~ns-eh2-prod-am3-516.cloudapp.net [13.69.64.0]) - [ ] Namespace should be either Standard or Dedicated tier, not Basic (TopicAuthorization errors)
