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

Schema fixes + avoiding duplicate reply begin on mqtt-kafka subscribe stream #872

Merged
merged 11 commits into from
Mar 25, 2024

Conversation

bmaidics
Copy link
Contributor

No description provided.

"additionalProperties": false
},
"additionalProperties": false
"$ref": "#/$defs/options/binding/mqtt-kafka/topics"
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not sure about this one, since we're deliberately using channels asyncapi concept here, whereas mqtt-kafka deals with kafka-specific topics instead, so unifying this config causes asyncapi to switch to topics instead.

"messages"
],
"additionalProperties": false
"$ref": "#/$defs/options/binding/mqtt-kafka/topics"
Copy link
Contributor

Choose a reason for hiding this comment

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

See feedback on asyncapi options for mqtt-kafka.

@jfallows jfallows merged commit d14fafe into aklivity:develop Mar 25, 2024
5 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.

2 participants