0dc26ba483
fix: create new version
2022-04-13 15:01:47 +08:00
6600de710a
fix: fix behavior of rule-engine when selection field does not exist
...
when the selection field does not exist, it should output field => undefined
2022-04-13 14:55:43 +08:00
73ac4c1ff8
fix: random id ensure do not delete resource
2022-04-11 18:33:20 +08:00
8530ecec4d
fix: delete a resource before updating it
2022-04-08 11:46:10 +08:00
adf7d53ca5
fix: use concat replace flatten
2022-04-08 10:27:28 +08:00
7606f55673
fix: update emqx_rule_engine.appup.src
2022-04-08 10:17:18 +08:00
96b26bf4ce
fix: discard rpc call failed data
2022-04-08 10:12:40 +08:00
16dc0d6555
Merge pull request #7536 from EMQ-YangM/reset_cluster_metrics
...
feat: impl reset cluster metrics
2022-04-07 11:31:49 +08:00
75486efb11
Merge pull request #7534 from EMQ-YangM/dev/v4.3.14
...
fix: change rule_speed record type
2022-04-07 10:37:27 +08:00
1c32b08b21
feat: impl reset cluster metrics
2022-04-07 10:32:58 +08:00
0e02e8df9d
fix: change rule_speed record type
2022-04-07 09:50:31 +08:00
a1705f5653
fix: flaky test
2022-04-06 09:11:09 -03:00
1a715c8708
feat(emqx_dashboard): subsciption to update password
...
emqx_dashboard restarted in ekka hook
Closes #3155
2022-04-05 10:40:09 +02:00
5b58eaa203
refactor(emqx_rule_engine): return not raise error for known reasons
2022-04-04 19:10:52 +02:00
67ce53b5fc
fix(appup): re-generated emqx_rule_engine.appup.src
2022-04-02 23:25:36 +02:00
a54813dd69
fix(appup): re-generate appup from 4.3.13
2022-04-02 23:00:41 +02:00
299c369d80
feat: enhanced rule engine error handling when json parsing error
2022-04-02 16:24:07 +08:00
b84ef11935
Merge branch 'dev/v4.3.14' into dev/v4.3.14
2022-04-01 09:32:42 +08:00
3cc0bb8284
Merge branch 'dev/v4.3.14' into fix_patter_match_v4.3
2022-04-01 09:14:34 +08:00
326634c287
feat: impl api PUT /rules/{id}/reset_metrics
2022-03-31 18:00:57 +08:00
510e4d31e4
fix: load_module emqx_rule_events
2022-03-31 13:48:12 +08:00
cead8c9056
fix: use masp:get/3 to avoid crash after match failure
2022-03-30 09:44:06 +08:00
6ab0934674
fix(rule): connection test when creating a resource
2022-03-30 09:23:51 +08:00
4ee586a738
fix: appup.src
2022-03-29 17:12:35 +08:00
a1a37bcbee
feat: Add mongo_date function to support saving timestamp as MongoDB Date object
2022-03-25 17:43:32 +01:00
b76372e621
chore: remove duplicated emqx_rule_funcs in appup.src
2022-03-23 19:29:58 +08:00
0d55b9242d
Merge branch 'main-v4.3' into resource_get_status_timeout
2022-03-23 17:59:59 +08:00
e8c7388aa4
chore: update appup file for emqx_rule_engine
2022-03-23 16:21:27 +08:00
b993595c6d
fix: add emqx_rule_funcs to appup.src
2022-03-23 15:42:53 +08:00
5275e6a30f
fix(rule): get the cached status when calling emqx_rule_engine:get_resource_status/1
2022-03-23 15:33:50 +08:00
62eff94249
feat(emqx_rule_funcs): add functions gzip, gunzip, zip, unzip
2022-03-22 15:16:31 +08:00
5823751d7d
chore: bump emqx_rule_engine to 4.3.9
2022-03-18 18:28:30 +08:00
81ae2be760
fix(rules): enlarge precisions of floats to maximum 17 decimal places.
...
When printing floats to strings, we have to define a small decimal
limits to avoid print a too long and "inaccurate" float number:
```
2> float_to_binary(0.3).
<<"2.99999999999999988898e-01">>
```
This fix sets precision of floats to 17 digits after the decimal point.
This precision is larger than precision of most `double` data type used by
databases(14 digits for mysql and 15 digits for pgsql).
2022-03-18 15:42:01 +08:00
cca9e52c9a
chore(appup): add missing appup instructions
2022-03-01 11:41:52 +01:00
cf1cc7e9db
chore(appup): update appup files
2022-02-24 17:14:47 -03:00
43c900bb5a
chore: rename more descriptive EQM X to EMQX
2022-02-22 11:16:38 +01:00
a5f6e94467
docs: EMQ X -> EMQX
2022-02-15 22:12:46 +01:00
e09e5673eb
docs(README): EMQ X -> EMQX
2022-02-15 16:15:25 +01:00
fdef292ef7
fix(appup): rm redundant `load_module` instruction after `update`
2022-02-10 09:31:36 -03:00
e053700441
style: please elvis checks
2022-02-09 11:02:05 -03:00
5e223ac64f
chore(appup): update appup files
2022-02-09 09:54:39 -03:00
b968d4c416
fix(ctl): fix formatting when printing messages without arguments (4.3)
...
Without passing an empty argument list to `emqx_ctl:print`, formatting
instructions like `~n` are being printed literally.
```
Ignore.~nJoin the cluster successfully.~nCluster status: #{running_nodes =>
['emqx@emqx-0.int.thalesmg','emqx@emqx-1.int.thalesmg',
'emqx@emqx-2.int.thalesmg','emqx@emqx-3.int.thalesmg',
'emqx@emqx-4.int.thalesmg'],
stopped_nodes => []}
```
2022-02-09 09:36:27 -03:00
03d240c59e
fix(emqx_rule_engine_metrics): fix code_change vsn value
2022-01-24 11:14:31 +08:00
2d00373e49
fix(appup): update appup file for emqx_rule_engine_api
2022-01-19 19:51:25 +08:00
70c6ac4e0d
fix(rule): deny POST rules or resources with empty ids
2022-01-19 19:22:25 +08:00
eec566fe40
fix(rule): restore the metrics for actions in cluster
2022-01-14 10:33:32 +08:00
4abcab8d52
fix(appup): update appup files for emqx,emqx_sn,rule_engine
2022-01-13 18:37:22 +08:00
9f7f5070b2
fix(channel): update the calls to emqx_session APIs
2022-01-13 13:33:27 +08:00
217acc0154
feat(rule): add new event 'delivery_dropped'
2022-01-12 20:11:08 +08:00
da8cd5d103
fix(rule_engine_metrics): fxi string:to_integer pattern match error
2022-01-11 22:09:38 -08:00
EMQ-YangM