[
https://issues.apache.org/jira/browse/JAMES-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3768.
---------------------------------
Resolution: Fixed
> Allow fully disactivate the Cassandra part of the RabbitMQ mail queue
> ---------------------------------------------------------------------
>
> Key: JAMES-3768
> URL: https://issues.apache.org/jira/browse/JAMES-3768
> Project: James Server
> Issue Type: Task
> Reporter: Benoit Tellier
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> To quote
> https://www.mail-archive.com/[email protected]/msg71989.html
> Some project members have expressed concerns regarding the current
> distributed application and its rabbitMQ mail queue. The "management" part of
> this mail queue was implemented in cunjunction with Cassandra and lead to
> complex code that is hard to maintain and hard to operate. The "delay"
> feature (that makes management features needed!) is not supported. On the
> long term the project expressed its interest for having a Pulsar based
> distributed server. However on the short term, and in order to support this
> deprecation, I propose to allow simplifying the RabbitMQ by adding an option
> not to activate "management features".
> Given that is behaves as a pure message queue (no delays), for a MDA looking
> into and interfering with a mail queue makes little sense (and I never did).
> Adding an option to drop this complexity, disable
> browse/flush/size/remove/clear would allow to have a simple yet reliable mail
> queue suited to a MDA in the waiting of the Pulsar alternative.
> h3. Proposal
> A module chooser, that provides either the Cassandra implementation or a
> throwing one based on the `mailqueue.view.enabled=true` property within
> `rabbitmq.properties`.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
