Struktur: 3cf18a293d

Shawn 3ca3470844 fix(rule_events): add descs for test columns		vor 4 Jahren
..
etc	6903997b94 feat(connector): add new option 'mode' to mqtt connectors	vor 4 Jahren
include	5c6e3fce6a refactor: update postgres connector tests to use resource apis	vor 4 Jahren
src	247b14c95f fix(mqtt_bridge): refine the message format from a mqtt bridge source	vor 4 Jahren
test	3ca3470844 fix(rule_events): add descs for test columns	vor 4 Jahren
.gitignore	54dedc8343 Revert "chore: mv emqx_connector to emqx_data_bridge"	vor 4 Jahren
README.md	e54f4b75da fix(emqx_connector): fix resource status	vor 4 Jahren
rebar.config	b383e68c94 fix: update mongodb client to latest version with deadloop fix	vor 4 Jahren

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 => connected}]
(emqx@127.0.0.1)6> emqx_resource:query(<<"mysql-abc">>, {sql, <<"SELECT count(1)">>}).
{ok,[<<"count(1)">>],[[1]]}

README.md

emqx_connector