Found some trouble with MQTT component
if used OR ssl OR name/password authorisation - all work fine,
but if enable both - it not work
the problem is, Talend use the same name for password variable
and for user credentials and for KeyStore (for TrustStore - variable name different)
Solution - is not use authentication in Fabric, and add UserName/Password as parameters in cMQTT component
error same in 6.2.2 and 6.3.1
Last edited by vapukov (2017-03-19 15:09:35)
it work as I describe, but good to have it fixed in feature
If I can ask You - any method to manage offset with MQTT? I just can't found - how
What I mean - other tools such as NiFi allow or continue session after restart, or reset it and start from scratch (in case of re-loading topic data). Is it possible?
You are right, look like it my wrong understanding topics in MQTT
so the question it cancelled
I just was not correct understand this settings:
but tests confirm - it always start from current messages and no chances to read topic in past.
will read more about MQTT
Last edited by vapukov (2017-03-20 23:11:42)
For MQTT you can only read the latest from the queue. In particular of you acknowledge the message is "gone".
Kafka operates differently where you have a ringbuffer. Thus, Kafka allows to resume reading from a different offset then last.