History

zhouzb e2676bcbd8 fix: fix dep of epgsql		2022-01-13 11:39:48 +08:00
..
etc	feat(connector): add new option 'mode' to mqtt connectors	2021-12-07 09:56:57 +08:00
include	chore: rename required function to not_empty	2021-07-09 14:18:41 +08:00
src	fix: return error when parse failed	2022-01-13 11:15:08 +08:00
test	fix(test): flaky emqx_connector_api_SUITE test case.	2022-01-07 14:45:47 +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: fix dep of epgsql	2022-01-13 11:39:48 +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]]}