zmstone
zmstone
it is now irrelevant because there is only Enterprise edition starting from 5.9.
It should work if you configure connector with `url = "https://eu-central-1-1.aws.cloud2.influxdata.com:443"` and move the path parts to the action `path = "/api/v2/write?bucket=my-bucket&precision=ms"`
IMO. connector should not have supported path in the first place, but for completeness, i have sent a PR to fix the bad `/` insertion. #13687 , targeting 5.8.1
EDIT: sorry, misunderstood the requirement. please ignore. ~In EMQX 5.8 Enterprise edition, there is going to be a message transformation feature which can do more than auto-subscribe.~ ~There is no...
@tgwzwu thank you. this is likely a bug. I cannot seem to find the node-down clean up code for exclusive-subscriptions.
for internal ref, created issue tracker: https://emqx.atlassian.net/browse/EMQX-12707
A recap: The PRs merged so far are mitigations not fixes. https://github.com/emqx/emqx/pull/13515 allows the same client to subscribe again. https://github.com/emqx/emqx/pull/13524 allows user to manually delete a clientID topic bind to...
Will message is denied by ACL because EMQX expires the connection **after** authentication data is expired. The fix is simple, EMQX should expire the connection 1 second (or 2~5 seconds...
> Yes, this is exactly what is written at the spec. However, since the message is stored in the session, it must be published on behalf of the client who...
for internal ref: https://emqx.atlassian.net/browse/EMQX-12708