History

William Yang 9c8cd6c437 perf(pool): change emqx_connector default pool type to hash		2021-10-27 08:47:02 +02:00
..
include	chore: rename required function to not_empty	2021-07-09 14:18:41 +08:00
src	perf(pool): change emqx_connector default pool type to hash	2021-10-27 08:47:02 +02:00
test	refactor(bridges): move some test cases from old emqx_bridge_mqtt app	2021-09-10 11:43:03 +08:00
.gitignore	Revert "chore: mv emqx_connector to emqx_data_bridge"	2021-06-17 19:11:10 +08:00
README.md	Revert "chore: mv emqx_connector to emqx_data_bridge"	2021-06-17 19:11:10 +08:00
rebar.config	fix(mongo): update the health check method	2021-10-19 15:52:36 +08:00

README.md

emqx_connector

This application is a collection of connectors.

A connector is a callback module of emqx_resource that maintains the data related to external resources. Put all resource related callback modules in a single application is good as we can put some util functions/modules here for reusing purpose.

For example, a mysql connector is an emqx resource that maintains all the mysql connection related parameters (configs) and the TCP connections to the mysql server.

An mysql connector can be used as following:

(emqx@127.0.0.1)5> emqx_resource:list_instances_verbose().
[#{config =>
       #{auto_reconnect => true,cacertfile => [],certfile => [],
         database => "mqtt",keyfile => [],password => "public",
         pool_size => 1,
         server => {{127,0,0,1},3306},
         ssl => false,user => "root",verify => false},
   id => <<"mysql-abc">>,mod => emqx_connector_mysql,
   state => #{poolname => 'mysql-abc'},
   status => started}]
(emqx@127.0.0.1)6> emqx_resource:query(<<"mysql-abc">>, {sql, <<"SELECT count(1)">>}).
{ok,[<<"count(1)">>],[[1]]}