Open smaktacular opened 3 years ago
Hi, this is your first issue in IoTDB project. Thanks for your report. Welcome to join the community!
I can reproduce this issue with 0.12 source code, but from my server logs which indicate the builtin moquette does not support '#' wildcards, @smaktacular you can replace '#' with any others, as the topic is useless for iotdb in current version.
Caused by: io.netty.handler.codec.DecoderException: invalid publish topic name: # (contains wildcards) at io.netty.handler.codec.mqtt.MqttDecoder.decodePublishVariableHeader(MqttDecoder.java:274) at io.netty.handler.codec.mqtt.MqttDecoder.decodeVariableHeader(MqttDecoder.java:198) at io.netty.handler.codec.mqtt.MqttDecoder.decode(MqttDecoder.java:88) at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:489) at io.netty.handler.codec.ReplayingDecoder.callDecode(ReplayingDecoder.java:367)
Is your feature request related to a problem? Please describe. I like the idea of the integrated mqtt service. But I already have configured all my devices to a dedicated broker (mosquitto). I am now looking for an easy way to bridge my existing broker to the integrated mqtt service.
Describe the solution you'd like Allow bridging from other brokers like e.g. Mosquitto
Describe alternatives you've considered Create a dedicated client that subscribes to # and forwards all messages to IOTDB and vice versa.
Additional context Mosquitto.conf: persistence true persistence_location /mosquitto/data/ log_dest file /mosquitto/log/mosquitto.log
connection iotdbltbridge address 192.168.1.13 topic # remote_username root remote_password ****
When trying to setup a bridge on mosquitto side I get an exception on IOTDB side: