emqx/apps/emqx_bridge_pulsar
Thales Macedo Garitezi b609792a90 fix(pulsar_producer): do not return `disconnected` when checking status (r5.1)
Fixes https://emqx.atlassian.net/browse/EMQX-10278

Since Pulsar client has its own replayq that lives outside the management of the buffer
workers, we must not return disconnected status for such bridge: otherwise, the resource
manager will eventually kill the producers and data may be lost.
2023-06-13 11:44:45 -03:00
..
etc feat: implement Pulsar Producer bridge (e5.0) 2023-04-24 10:28:26 -03:00
include feat: implement Pulsar Producer bridge (e5.0) 2023-04-24 10:28:26 -03:00
src fix(pulsar_producer): do not return `disconnected` when checking status (r5.1) 2023-06-13 11:44:45 -03:00
test fix(pulsar_producer): do not return `disconnected` when checking status (r5.1) 2023-06-13 11:44:45 -03:00
.gitignore feat: implement Pulsar Producer bridge (e5.0) 2023-04-24 10:28:26 -03:00
BSL.txt feat: implement Pulsar Producer bridge (e5.0) 2023-04-24 10:28:26 -03:00
README.md docs: hide the not-ready document links 2023-05-15 11:20:23 +08:00
docker-ct feat: implement Pulsar Producer bridge (e5.0) 2023-04-24 10:28:26 -03:00
rebar.config fix(pulsar): update pulsar -> 0.8.3 2023-06-12 10:29:40 -03:00

README.md

Pulsar Data Integration Bridge

This application houses the Pulsar Producer data integration bridge for EMQX Enterprise Edition. It provides the means to connect to Pulsar and publish messages to it.

Currently, our Pulsar Producer library has its own replayq buffering implementation, so this bridge does not require buffer workers from emqx_resource. It implements the connection management and interaction without need for a separate connector app, since it's not used by authentication and authorization applications.

Documentation links

For more information on Apache Pulsar, please see its official site.

Contributing

Please see our contributing.md.

License

EMQ Business Source License 1.1, refer to LICENSE.