MQTT wildcard and prefix fix#2149
Open
Woestebanaan wants to merge 1 commit intolensesio:masterfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously, the
$wildcard in KCQL target mappings only worked as a standalone value —getTargethad to return exactly"$"for the MQTT source topic to be used as the target. If a user wrote something like"prefix_$"or"data/$_events", the$would not be substituted and the literal string (including$) would be used as-is.This change adds support for
$as an embedded placeholder within a larger target string. The sanitized MQTT topic name is now substituted wherever$appears in the target.Examples:
Also fixed the single and multi-level MQTT wildcards
Resolved the following issue: #1386