[
https://issues.apache.org/jira/browse/MINIFICPP-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Hunyadi updated MINIFICPP-1291:
------------------------------------
Description:
MQTT processors are untested and unstable (based on the latest commit fixing
them).
A 3rd party should be found to act as other end of the mqtt communication and
verify the processors.
*Update 1:*
[[Mosquitto]|https://github.com/eclipse/mosquitto] should be a good candidate
as a third-party handling MQTT communication. It is licensed under the
[[Eclipse Public License 1.0]|https://www.eclipse.org/legal/epl-v10.html] which
is [[compatible with the Apache
License]|https://www.apache.org/legal/resolved.html].
*Update 2:*
Seems like mosquitto does not actually provide an c++ library interface for
running a broker, only clients are available. I misunderstood "is an opensource
MQTT broker and provides client library implementation for MQTT." for "is an
opensource MQTT broker and client library implementation. Marton is completely
right with his comment.
However, this means that we could not find any candidate library that allows us
testing from within our c++ integration tests only. We should find a dockerized
broker container and use that instead. Closing this ticket and
was:
MQTT processors are untested and unstable (based on the latest commit fixing
them).
A 3rd party should be found to act as other end of the mqtt communication and
verify the processors.
*Update 1:*
[[Mosquitto]|https://github.com/eclipse/mosquitto] should be a good candidate
as a third-party handling MQTT communication. It is licensed under the
[[Eclipse Public License 1.0]|https://www.eclipse.org/legal/epl-v10.html] which
is [[compatible with the Apache
License]|https://www.apache.org/legal/resolved.html].
*Update 2:*
Seems like mosquitto does not actually provide an c++ library interface for
running a broker, only clients are available. I misunderstood "is an opensource
MQTT broker and provides client library implementation for MQTT." for "is an
opensource MQTT broker and client library implementation. Marton is completely
right with his comment.
However, this means that we could not find any candidate library that allows us
testing
> Update MQTT processors so that they use the Mosquitto third-party
> -----------------------------------------------------------------
>
> Key: MINIFICPP-1291
> URL: https://issues.apache.org/jira/browse/MINIFICPP-1291
> Project: Apache NiFi MiNiFi C++
> Issue Type: Improvement
> Reporter: Arpad Boda
> Assignee: Adam Hunyadi
> Priority: Major
> Labels: MiNiFi-CPP-Hygiene
> Time Spent: 10m
> Remaining Estimate: 0h
>
> MQTT processors are untested and unstable (based on the latest commit fixing
> them).
> A 3rd party should be found to act as other end of the mqtt communication
> and verify the processors.
> *Update 1:*
> [[Mosquitto]|https://github.com/eclipse/mosquitto] should be a good candidate
> as a third-party handling MQTT communication. It is licensed under the
> [[Eclipse Public License 1.0]|https://www.eclipse.org/legal/epl-v10.html]
> which is [[compatible with the Apache
> License]|https://www.apache.org/legal/resolved.html].
> *Update 2:*
> Seems like mosquitto does not actually provide an c++ library interface for
> running a broker, only clients are available. I misunderstood "is an
> opensource MQTT broker and provides client library implementation for MQTT."
> for "is an opensource MQTT broker and client library implementation. Marton
> is completely right with his comment.
> However, this means that we could not find any candidate library that allows
> us testing from within our c++ integration tests only. We should find a
> dockerized broker container and use that instead. Closing this ticket and
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
