You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Tellier Benoit (JIRA)" <se...@james.apache.org> on 2018/12/06 08:08:00 UTC

[jira] [Commented] (JAMES-2550) geable RabbitMQ: delete

    [ https://issues.apache.org/jira/browse/JAMES-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711102#comment-16711102 ] 

Tellier Benoit commented on JAMES-2550:
---------------------------------------

https://github.com/linagora/james-project/pull/1942 proposed a reactor stream implementation to better handle concurrency

> geable RabbitMQ: delete
> -----------------------
>
>                 Key: JAMES-2550
>                 URL: https://issues.apache.org/jira/browse/JAMES-2550
>             Project: James Server
>          Issue Type: New Feature
>            Reporter: Antoine Duprat
>            Priority: Major
>             Fix For: 3.2.0
>
>
> 1. query all messages in time range [current message timestamp:now]
> 2. apply deletion on the given message set
> 3. store deleted message ids
> Update dequeue and browse appropriately.
> For example for dequeue, you'll need to check if the message is in the deleted message ids before returning it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org