|
|
3 лет назад | |
|---|---|---|
| .. | ||
| etc | 8aa60cc0a5 feat: generate a minimized emqx.conf | 3 лет назад |
| i18n | 09455edae8 Merge tag 'v5.0.10' into dev/ee5.0 | 3 лет назад |
| include | c157392452 docs: fix self-closing html tag, change </br> to <br/> | 3 лет назад |
| src | 1c2fc4b6c3 Merge remote-tracking branch 'origin/release-50' into 1206-chore-merge-ee50-to-release-50 | 3 лет назад |
| test | 275171d217 feat: handle lists of servers in mongo servers config | 3 лет назад |
| .gitignore | 54dedc8343 Revert "chore: mv emqx_connector to emqx_data_bridge" | 4 лет назад |
| README.md | e54f4b75da fix(emqx_connector): fix resource status | 4 лет назад |
| docker-ct | f785da075b ci: only start required docker for integration tests | 3 лет назад |
| rebar.config | a6eff81163 chore: update emqtt to 1.7.0-rc.1 | 3 лет назад |
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]]}