[
https://issues.apache.org/jira/browse/NIFI-11270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706606#comment-17706606
]
ASF subversion and git services commented on NIFI-11270:
--------------------------------------------------------
Commit 2b9f2071ed111f461236900277976f91bc1ac029 in nifi's branch
refs/heads/main from Nandor Soma Abonyi
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2b9f2071ed ]
NIFI-11270 Refactoring of the overly Paho-specific MQTT interface
This closes #7032.
Signed-off-by: Peter Turcsanyi <[email protected]>
> Refactoring of the overly Paho-specific MQTT interface
> ------------------------------------------------------
>
> Key: NIFI-11270
> URL: https://issues.apache.org/jira/browse/NIFI-11270
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Nandor Soma Abonyi
> Assignee: Nandor Soma Abonyi
> Priority: Minor
> Labels: mqtt
> Fix For: 1.latest, 2.latest
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> ConsumeMQTT processor implements the MqttClient interface, which follows the
> signature of the Paho library's MqttClient interface. There are two issues
> with that. It mixes two types of behavior because the client itself can act
> as a publisher and subscriber parallelly. However, in NiFi, these two roles
> are separated into different processors. So it doesn't make sense to
> implement the subscribe interface in PublishMQTT, and it also doesn't make
> sense to implement deliveryComplete in ConsumeMQTT.
> The other issue is that these interfaces cannot be used with the HiveMQ
> client except messageArrived(). Because of the above, we need to move the
> existing implementation into the Paho adapter (because it is still required
> for logging) and create a new interface for handling incoming messages.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
