Pulsar Bridge

    After EMQX version 3.1, a powerful rule engine is introduced to replace plug-ins. It is recommended that you use it. See Bridge data to Pulsar to setup pulasr bridges in rule engine.

    EMQX bridges and forwards MQTT messages to Pulsar cluster:

    Configure Pulsar Bridge Hooks

    2. ## ${topic}: the pulsar topics to which the messages will be published.
    3. ## ${filter}: the mqtt topic (may contain wildcard) on which the action will be performed .
    5. ## Client Connected Record Hook
    6. bridge.pulsar.hook.client.connected.1     = {"topic": "client_connected"}
    8. ## Client Disconnected Record Hook
    9. bridge.pulsar.hook.client.disconnected.1  = {"topic": "client_disconnected"}
    11. ## Session Subscribed Record Hook
    12. bridge.pulsar.hook.session.subscribed.1   = {"filter": "#",  "topic": "session_subscribed"}
    14. ## Session Unsubscribed Record Hook
    15. bridge.pulsar.hook.session.unsubscribed.1 = {"filter": "#",  "topic": "session_unsubscribed"}
    17. ## Message Publish Record Hook
    18. bridge.pulsar.hook.message.publish.1      = {"filter": "#",  "topic": "message_publish"}
    20. ## Message Delivered Record Hook
    21. bridge.pulsar.hook.message.delivered.1    = {"filter": "#",  "topic": "message_delivered"}
    23. bridge.pulsar.hook.message.acked.1        = {"filter": "#",  "topic": "message_acked"}
    25. ## More Configures
    26. ## partitioner strategy:
    27. ## Option:  random | roundrobin | first_key_dispatch
    28. ## Example: bridge.pulsar.hook.message.publish.1 = {"filter":"#", "topic":"message_publish", "strategy":"random"}
    31. ## Option: ${clientid} | ${username}
    32. ## Example: bridge.pulsar.hook.message.publish.1 = {"filter":"#", "topic":"message_publish", "key":"${clientid}"}
    34. ## format:
    35. ## Option: json | json
    36. ## Example: bridge.pulsar.hook.message.publish.1 = {"filter":"#", "topic":"message_publish", "format":"json"}

    Description of Pulsar Bridge Hooks

    Client goes online, EMQX forwards ‘client_connected’ event message to Pulsar:

    1. topic = "client_connected",
    2. value = {
    3.          "client_id": ${clientid},
    4.          "username": ${username},
    5.          "node": ${node},
    6.          "ts": ${ts}
    7.         }

    Client goes offline, EMQX forwards ‘client_disconnected’ event message to Pulsar:

    1. topic = "client_disconnected",
    2. value = {
    3.          "client_id": ${clientid},
    4.          "username": ${username},
    5.          "reason": ${reason},
    6.          "node": ${node},
    7.          "ts": ${ts}
    8.         }

    Forward Subscription Event to Pulsar

    Forward Unsubscription Event to Pulsar

    1. topic = session_unsubscribed
    3. value = {
    4.          "client_id": ${clientid},
    5.          "qos": ${qos},
    6.          "node": ${node},
    7.          "ts": ${timestamp}
    1. topic = message_publish
    3. value = {
    4.          "client_id": ${clientid},
    5.          "username": ${username},
    6.          "topic": ${topic},
    7.          "payload": ${payload},
    8.          "qos": ${qos},
    9.          "node": ${node},
    10.          "ts": ${timestamp}
    11.         }

    Forwarding MQTT Message Deliver Event to Pulsar

    1. topic = message_delivered
    3. value = {"client_id": ${clientid},
    4.          "username": ${username},
    5.          "from": ${fromClientId},
    6.          "topic": ${topic},
    7.          "payload": ${payload},
    8.          "qos": ${qos},
    9.          "node": ${node},
    10.          "ts": ${timestamp}
    11.         }

    Forwarding MQTT Message Ack Event to Pulsar

    Pulsar consumes MQTT clients connected / disconnected event messages:

    1. sh pulsar-client consume client_connected  -s "client_connected" -n 1000
    3. sh pulsar-client consume client_disconnected  -s "client_disconnected" -n 1000
    1. sh pulsar-client consume session_subscribed  -s "session_subscribed" -n 1000
    3. sh pulsar-client consume session_unsubscribed  -s "session_unsubscribed" -n 1000

    Pulsar consumes MQTT published messages:

    1. sh pulsar-client consume message_publish  -s "message_publish" -n 1000

    Pulsar consumes MQTT message Deliver and Ack event messages:

    TIP

    Enable Pulsar Bridge