History

Thales Macedo Garitezi 25b0e31035 fix(kafka_producer): do not return disconnected when checking status (r5.1) Fixes https://emqx.atlassian.net/browse/EMQX-10279 Related: https://github.com/emqx/emqx/pull/11038 Since wolff 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 13:54:57 -03:00
..
etc	refactor(kafka_bridge): move kafka bridge into its own app	2023-04-12 13:54:45 -03:00
src	fix(kafka_producer): do not return disconnected when checking status (r5.1)	2023-06-13 13:54:57 -03:00
test	test: rm unused var warnings	2023-06-12 15:19:47 -03:00
BSL.txt	refactor(kafka_bridge): move kafka bridge into its own app	2023-04-12 13:54:45 -03:00
README.md	docs: fix invalid links	2023-05-15 11:18:09 +08:00
docker-ct	refactor(kafka_bridge): move kafka bridge into its own app	2023-04-12 13:54:45 -03:00
rebar.config	chore: bump dependency vsn	2023-05-30 11:11:30 +08:00

README.md

Kafka Data Integration Bridge

This application houses the Kafka Producer and Consumer data integration bridges for EMQX Enterprise Edition. It provides the means to connect to Kafka and publish/consume messages to/from it.

Currently, our Kafka Producer library (wolff) 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 about Apache Kafka, please see its official site.

Configurations

Please see Ingest Data into Kafka for more detailed info.

Contributing

Please see our contributing.md.

License

EMQ Business Source License 1.1, refer to LICENSE.