History

Shawn 1de2f5cb2f fix(emqx_data_bridge): update bridge failed		2021-06-08 21:46:52 +08:00
..
etc	feat(emqx_data_bridge): create emqx_data_bridge	2021-06-04 23:47:16 +08:00
priv	feat(emqx_data_bridge): create emqx_data_bridge	2021-06-04 23:47:16 +08:00
src	fix(emqx_data_bridge): update bridge failed	2021-06-08 21:46:52 +08:00
.gitignore	feat(emqx_connector): add first emqx_connector for mysql	2021-05-31 15:14:07 +08:00
README.md	feat(emqx_data_bridge): create emqx_data_bridge	2021-06-04 23:47:16 +08:00
rebar.config	feat(emqx_connector): add first emqx_connector for mysql	2021-05-31 15:14:07 +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]]}