Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support topic pattern wildcards in mqtt-kafka clients #1178

Closed
jfallows opened this issue Aug 4, 2024 · 0 comments · Fixed by #1179
Closed

Support topic pattern wildcards in mqtt-kafka clients #1178

jfallows opened this issue Aug 4, 2024 · 0 comments · Fixed by #1179
Assignees
Labels
bug Something isn't working

Comments

@jfallows
Copy link
Contributor

jfallows commented Aug 4, 2024

Describe the bug
mqtt-kafka clients topic patterns do not match all required topics according to MQTT specification wildcard pattern matching rules.

To Reproduce
Steps to reproduce the behavior:

  1. Go to aklivity/zilla-examples repo, mqtt.kafka.broker example.
  2. Modify docker/compose/setup.sh to create mqtt-devices topic with multiple partitions.
  3. Modify zilla.yaml north_mqtt_kafka_mapping clients option to place/{identity}/+/#.
  4. Publish messages for same identity, but different devices.
  5. Observe that messages for different devices but same identity can arrive on different mqtt-devices partitions.

Expected behavior
Messages for different devices but same identity should always arrive on the same mqtt-devices partitions.

Screenshots
None

Zilla Environment:

ZILLA_VERSION=0.9.89
@jfallows jfallows added the bug Something isn't working label Aug 4, 2024
@jfallows jfallows self-assigned this Aug 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant