f01de238b2
chore: bump app vsns
2023-06-22 10:01:12 -03:00
04bd39861d
chore: bump app vsns
2023-05-30 11:08:20 -03:00
36e268c933
chore: bump app versions
2023-05-26 16:05:37 +02:00
f83f9a2d79
chore: bump app vsns
2023-05-17 14:56:11 -03:00
bce43978a2
refactor: the clickhouse bridge to use the new bridge app structure
...
Fixes:
https://emqx.atlassian.net/browse/EMQX-9538
2023-05-17 10:12:43 +02:00
6497bcae46
refactor(influxdb): move influxdb bridge into its own app
2023-05-12 11:48:49 +08:00
8914e006c2
refactor(dynamo): move dynamo bridge into its own app
2023-05-10 18:49:21 +08:00
0f979b3d24
refactor(tdengine): move tdengine bridge into its own app
2023-05-10 14:12:57 +08:00
70cf1533db
feat: add RabbitMQ bridge
2023-05-09 14:32:26 +02:00
a119100a0e
refactor(rocketmq): move rocketmq bridge into its own app
2023-05-09 15:57:56 +08:00
d5dce771bd
refactor(sqlserver): move sqlserver bridge into its own app
2023-05-06 10:22:05 +08:00
dd90b2f498
feat(oracle): Oracle Database integration
2023-04-27 13:07:20 -03:00
ad4be08bb2
feat: implement Pulsar Producer bridge (e5.0)
...
Fixes https://emqx.atlassian.net/browse/EMQX-8398
2023-04-24 10:28:26 -03:00
5074825075
feat(opents): OpenTSDB integration
2023-04-23 09:56:24 +08:00
a9bd91fcff
refactor(gcp_pubsub): move GCP PubSub Bridge to its own app
...
Fixes https://emqx.atlassian.net/browse/EMQX-9536
Note: since GCP PubSub is not shared by any authn/authz backend,
there's no need to separate its connector into another app.
2023-04-19 13:24:32 -03:00
9fc8a498f8
chore: bump apps versions
2023-04-17 09:09:08 +02:00
871ee90b3e
refactor(kafka_bridge): move kafka bridge into its own app
...
Fixes https://emqx.atlassian.net/browse/EMQX-9481
2023-04-12 13:54:45 -03:00
bdffa925db
chore: merge upstream/master release-50
2023-04-12 15:30:20 +02:00
1c8333030c
fix(kafka_producer): add back `is_buffer_supported` callback
...
Fixes https://emqx.atlassian.net/browse/EMQX-9366
This callback was accidentally removed while adding another feature,
which made the buffer workers to be used for this bridge while they
shouldn’t be.
2023-03-28 09:33:18 -03:00
dd996ad1dc
chore: bump app vsns
2023-03-24 21:47:15 +01:00
969fa03ecc
feat: implement kafka consumer
2023-03-16 13:43:01 -03:00
a86d06f043
chore: bump app versions following last merge-back
2023-03-10 16:44:15 +03:00
18ab7ed197
chore: bump app vsns
2023-03-06 15:31:28 -03:00
81adb02402
chore: bump apps version
2023-02-14 22:04:29 +08:00
a0100c0a4e
chore: bump app versions
2023-01-23 16:20:21 +01:00
f15b29b1ef
chore: upgrade app version
2023-01-13 18:22:29 +08:00
a5e3f6f05b
fix(kafka): Memory OLP is only applicable in linux systems
2022-12-28 15:31:53 +01:00
9e3da5b661
chore: bump app versions
2022-12-14 20:07:41 +01:00
fa90638de2
chore: add description to apps
2022-11-30 17:03:41 +01:00
c940b901f5
chore: fix app versions
2022-11-16 16:26:43 +01:00
57270fb8fc
feat: add support for counters and gauges to the Kafka Bridge
...
This commit adds support for counters and gauges to the Kafka Brige.
The Kafka bridge uses [Wolff](https://github.com/kafka4beam/wolff ) for
the Kafka connection. Wolff does its own batching and does not use the
batching functionality in `emqx_resource_worker` that is used by other
bridge types. Therefore, the counter events have to be generated by
Wolff. We have added
[telemetry](https://github.com/beam-telemetry/telemetry ) events to Wolff
that we hook into to change counters and gauges for the Kafka bridge. The
counter called `matched` does not depend on specific functionality of
any bridge type so the updates of this counter is moved higher up in the
call chain then previously so that it also gets updated for Kafka
bridges.
2022-10-10 14:40:57 -03:00
dfe14be8b2
chore: bump app vsns
2022-09-26 18:23:28 +08:00
0c1595be02
feat: Add Kafka connector
2022-09-13 19:46:56 +02:00
be6de4aad0
fix: ee bridge & connector remove app mod
2022-07-27 11:38:45 +08:00
e4eba157c3
feat: add emqx enterprise app connector & bridge
2022-07-25 09:36:45 +08:00
Thales Macedo Garitezi