Pil0tXia opened a new pull request, #4395:
URL: https://github.com/apache/eventmesh/pull/4395
<!--
### Contribution Checklist
- Name the pull request in the form "[ISSUE #XXXX] Title of the pull
request",
where *XXXX* should be replaced by the actual issue number.
Skip *[ISSUE #XXXX]* if there is no associated github issue for this
pull request.
- Fill out the template below to describe the changes contributed by the
pull request.
That will give reviewers the context they need to do the review.
- Each pull request should address only one issue.
Please do not mix up code from multiple issues.
- Each commit in the pull request should have a meaningful commit message.
- Once all items of the checklist are addressed, remove the above text and
this checklist,
leaving only the filled out template below.
(The sections below can be removed for hotfixes of typos)
-->
<!--
(If this PR fixes a GitHub issue, please add `Fixes #<XXX>` or `Closes
#<XXX>`.)
-->
Fixes #4390.
### Motivation
StartUp failure when using RabbitMQ as storage-plugin.
### Modifications
Realize the RabbitMQ admin-api to fulfuill SPI extension loading.
### Admin functions?
Based on the current implementation of
org.apache.eventmesh.storage.rabbitmq.producer.RabbitmqProducer, it is not
possible to display message counts per topic.
RabbitMQ itself does not retain consumed messages or record topic names; it
can only list exchanges and queues. The existing exchanges and queues are both
singular and fixed.
To display topics, it would be necessary to retrieve the topic name from
each message and use it to declare a corresponding queue. However, this
approach would incur additional overhead when receiving new topics.
While elevating the topic concept to a queue could address the issue of
"being able to track historical message counts for queues but not for topics,"
this approach aligns with the design philosophy of exchanges with TOPIC type.
However, considering the current limited demand within the community, I plan to
address startup errors and provide only limited management functionalities for
now.
Upon investigation, it appears that utilizing the RabbitMQ Management HTTP
API is a favorable approach to list queues and historical message counts.
### Relevant Bug
https://github.com/apache/eventmesh/issues/4394
### Documentation
- Does this pull request introduce a new feature? (no)
- If yes, how is the feature documented? (not applicable / docs / JavaDocs /
not documented)
- If a feature is not applicable for documentation, explain why?
- If a feature is not documented yet in this PR, please create a followup
issue for adding the documentation
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
