[
https://issues.apache.org/jira/browse/NIFI-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032444#comment-17032444
]
Kay-Uwe Moosheimer commented on NIFI-6856:
------------------------------------------
Please add "expressionLanguageSupported" to clientId in
AbstractMQTTProcessor.java and change
clientID = context.getProperty(PROP_CLIENTID).getValue();
to
clientID =
context.getProperty(PROP_CLIENTID).evaluateAttributeExpressions().getValue();
Doing so someone can use ${hostname} as clientId or if someone wants ${UUID()}
or anything else. And we don't force anyone to use UUID if s/he doesn't want to.
In my opinion, this would be more elegant for monitoring the connections at the
broker.
> 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: 20m
> 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)
