After adding `emqx_rule_engine` to the `app.src` file for
`emqx_ee_schema_registry` the test suites in `emqx_ee_schema_registry`
started to fail when they where run together with
`make "lib-ee/emqx_ee_schema_registry-ct"`. However, they still worked
when executed one by one with
`SUITE=lib-ee/emqx_ee_schema_registry/test/emqx_ee_schema_registry_http_api_SUITE.erl make ct-suite`.
The failure probably happened as this changed the application start
order. As `emqx_ee_schema_registry` only requires `emqx_rule_engine` to be
loaded, `emqx_rule_engine` can be put in the included_applications list in
the emqx_ee_schema_registry.app.src file instead (this solved the issue).
This commit decouples the emqx_rule_engine application from the
emqx_ee_schema_registry application by making it possible to register a
callback module that defines extra rule engine SQL functions instead of
calling a module in emqx_ee_schema_registry directly from the
emqx_rule_engine application.
Part of https://emqx.atlassian.net/browse/EMQX-9251
This ports part of the Schema Registry app from 4.x to 5.0. Here,
only support for Avro is added. Subsequent PRs will follow to add
support for other formats.
Part of https://emqx.atlassian.net/browse/EMQX-9251
This ports part of the Schema Registry app from 4.x to 5.0. Here,
only support for Avro is added. Subsequent PRs will follow to add
support for other formats.
Kjell Winblad