[
https://issues.apache.org/jira/browse/NIFI-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045998#comment-17045998
]
ASF subversion and git services commented on NIFI-6856:
-------------------------------------------------------
Commit 23b04ae96863fc3b0fd3b268bcb7d155edf17f26 in nifi's branch
refs/heads/master from Justin Miller
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=23b04ae ]
NIFI-6856 - Make client ID a non-required field for the MQTTConsume and
MQTTProduce processors. Generates a
random ID if not set.
Also add group ID field to ConsumeMQTT processor. Allows consumer to join
consumer group at $share/<group_id>/<topic_filter>
add expression language support for the MQTT client ID
Setting client id in publish test fails because it is not a flowfile attribute.
Remove client id and autogenerate it when testing.
Since the evaluation is done in onScheduled, there is no flow file available
and we're not using the attributes to make the expression language evaluation.
You can change the scope to use the Variable Registry.
Co-Authored-By: Pierre Villard <[email protected]>
Signed-off-by: Pierre Villard <[email protected]>
This closes #3879.
> Support MQTT consumer groups
> ----------------------------
>
> Key: NIFI-6856
> URL: https://issues.apache.org/jira/browse/NIFI-6856
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.11.0
> Reporter: Justin Miller
> Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Multiple MQTT brokers including HiveMQ and EMQX support MQTT consumer groups,
> which provide a way of horizontally scaling and load balancing MQTT
> consumers. This feature is built on the MQTTv5 protocol but all the logic is
> handled server side, so any MQTT client can take advantage of these features:
> [https://docs.emqx.io/tutorial/v3/en/advanced/share_subscribe.html.]
> Right now ConsumeMQTT cannot take advantage of this horizontal scaling
> because client ID is required and does not support expression language.
> Making the client id optional and defaulting to a uuid along with adding a
> group id field that sets the consumer to join the consumer group would open
> up the ability to take advantage of these broker features.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
