dd6b214231
fix: write quoted strings to influxdb failed
2024-01-12 20:11:22 +08:00
456a14fe20
fix: cannot write literal numbers to influxdb
2024-01-12 14:31:55 +08:00
7365160eeb
Merge pull request #12275 from thalesmg/sync-r54-m-20240108
...
sync r54 into master
2024-01-09 10:05:06 +08:00
7763b0fd34
chore: bump app vsns
2024-01-08 17:42:56 -03:00
756980837c
Merge branch 'release-54' into sync-r54-m-20240108
2024-01-08 17:39:42 -03:00
caf461fdf6
fix(ds): Don't start the supervision tree when feature is not in use
2024-01-08 17:59:19 +01:00
ec34b6f41d
refactor: remove redis_type from redis action
2024-01-08 15:09:37 +08:00
3404f39fd2
chore: remove redundant redis action swagger example
2024-01-08 10:45:54 +08:00
7f57ec47d5
Merge pull request #12261 from lafirest/fix/iotdb
...
feat(iotdb): improve the IoTDB bridge to v2 style
2024-01-08 09:46:07 +08:00
6f4b22e376
test(iotdb): add template test case for IoTDB
2024-01-06 21:32:37 +08:00
d221f34ce8
chore: bump version && update changes
2024-01-06 13:34:07 +08:00
e20b024b6e
fix(iotdb): fix iotdb testcases
2024-01-06 13:01:43 +08:00
803529968e
test(s3): fix httpc ssl opts
2024-01-05 19:35:13 +01:00
06117c3a33
Merge remote-tracking branch 'upstream/release-54' into 0105-sync-r54
2024-01-05 14:20:38 +01:00
d04ac08d1d
chore: release 5.4.1
2024-01-05 11:48:28 +01:00
d16458ccd0
feat(iotdb): improve the IoTDB bridge to v2 style
2024-01-05 16:54:31 +08:00
37feeed560
fix: judgment condition always failure
2024-01-05 14:23:15 +08:00
da3937b80e
Merge pull request #12247 from emqx/split_influxdb_connector_actions
...
refactor: split influxdb bridges to actions and connectors
2024-01-05 14:07:35 +08:00
2f08471303
fix: cannot found desc for influxdb_parameters
2024-01-05 11:59:13 +08:00
9714092525
fix: fix: update more influxdb testcases
2024-01-05 11:20:27 +08:00
304fe84434
fix(mysql): expect password may be missing from config
2024-01-04 15:16:27 +01:00
8ebd233a46
chore: update influxdb-erl to 1.1.12
2024-01-04 10:20:52 +08:00
90404b62a4
fix: incorrectly attempt to update the field value when the previous field don't have value
2024-01-04 10:12:34 +08:00
19e2ec9748
fix: update influxdb testcases
2024-01-03 18:39:29 +08:00
00e8a36dbe
fix: the API prompt garbled characters for updating the configuration
2024-01-03 15:34:45 +08:00
57c0a7c5ef
Merge pull request #12235 from zhongwencool/ft-config-update-api
...
fix: ft config update api return raw config
2024-01-03 14:07:22 +08:00
d4c83cf463
chore: tag 5.4.1-alpha.1
2024-01-02 14:37:45 +01:00
904bd0270f
chore: bump app versions
2024-01-02 18:04:06 +08:00
7c7a0b2172
refactor: split influxdb bridges to actions and connectors
2024-01-02 18:01:22 +08:00
a87df28dfc
Merge pull request #12243 from keynslug/fix/EMQX-11483/route-async-repl
...
fix(router): rely on local sync state updates to propagate routes
2023-12-29 16:31:00 +01:00
5c91984ad7
chore: leave comment describing need for tighter synchronization
2023-12-29 14:04:48 +01:00
9e0f3ce53b
feat(ds): restore original add_generation/update_db_config callback semantics
2023-12-29 13:12:15 +03:00
5e100f52b8
style: erlfmt all `rebar.config` files and `bin/nodetool`
2023-12-29 09:08:03 +08:00
a3f33cc8bc
chore: fix typos in code and suite
2023-12-29 09:07:51 +08:00
ed10827343
docs: README spell
2023-12-29 09:07:25 +08:00
b9627c420f
fix(router): rely on local sync state updates to propagate routes
...
Instead of (potentially lagging) global table state itself. Local
state should be the only source of truth anyway. Moreover,
synchronize parts of local state update logic through the broker
pool to ensure consistency.
The problem was that `emqx_router:has_route/2` check may observe a
stale route, which deletion is not yet replicated from the core node
to the local replicant node.
For example:
1. The only one subscriber per a given topic A unsubscribes from
a replicant node.
2. The route to A is deleted by the emqx_broker.
3. Mria makes RPC to a core node, it succeeds and returns.
4. The client resubscribes or another client subscribes to the same
topic A.
5. emqx_broker tries to add a route again:
`emqx_router:do_add_route(Topic)`.
6. `emqx_router` checks if the route is present.
7. The stale route is present because deletion not replicated yet,
so no route is being added.
8. Route deletion is replicated locally but it's too late:
we already have a local subscriber without a route.
Co-Authored-By: Serge Tupchii <serge.tupchii@protonmail.com>
2023-12-28 19:16:31 +01:00
331bfaa535
fix(broker): avoid reclaiming per-topic counter twice
2023-12-28 17:43:50 +01:00
a8cd609ff4
chore(broker): simplify subscribe code path
2023-12-28 17:43:42 +01:00
2b61f5290d
Merge pull request #12236 from zmstone/1227-ensure-short-mqtt-bridge-clientid
...
fix(bridge/mqtt): ensure short clientid
2023-12-28 16:06:09 +01:00
a6acebb4aa
Merge pull request #12240 from zhongwencool/ft-api-e-541
...
fix: return raw config when update ft's config
2023-12-28 22:25:22 +08:00
18dc9b2516
fix(s3): remove `emqx_bridge_http` from runtime dependencies
...
Otherwise it's impossible to test `emqx_s3` in isolation.
2023-12-28 14:13:22 +01:00
1d9374125c
chore: bump `emqx_s3` to 5.0.13
2023-12-28 14:12:33 +01:00
33ef964582
fix(s3): handle extra configured headers correctly
...
* Header names in config become atoms.
(Probably because of blanket `unsafe_atom_key_map/1` in `emqx_config`)
* Header names should be normalized to lowercase.
(Otherwise signature will be incorrect)
2023-12-28 13:55:05 +01:00
4669c4d552
fix(bridge/mqtt): ensure short clientid
...
Some mqtt brokers do not allow long client IDs.
To make it compatible with this limitation, this commit
tries to limit the number of bytes under 23 with a best-effort
attempt to derive it from the bridge name.
2023-12-28 11:53:27 +01:00
1fd67564ce
fix: return raw config when update ft's config
2023-12-28 14:49:36 +08:00
b6391cf18c
fix(bridge-http): compatible conf with the error format introduced in 5.3.2
2023-12-28 11:36:48 +08:00
e645fa4874
fix: ft config update api return raw config
2023-12-27 21:13:47 +08:00
423b8b4274
fix(emqx_opentelemetry): use converter to convert legacy metrics config
...
HOCON converter is cleaner and safer option,
that will also work for configurations defined in emqx.conf.
Previously used `upgrade_raw_conf/1` is currently not supported in hocon_cli (used in bin/emqx).
Fixes: EMQX-11643
2023-12-27 14:15:12 +02:00
711a9a06c8
Merge pull request #12221 from thalesmg/test-flaky-retry-m-20231222
...
test: reduce flakiness
2023-12-27 14:30:25 +08:00
11feab983f
fix: clean rpc_commit when force_leave cluster
2023-12-26 15:25:58 +08:00
Shawn