[
https://issues.apache.org/jira/browse/JAMES-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409828#comment-17409828
]
Benoit Tellier commented on JAMES-3109:
---------------------------------------
I'm wondering if this is a good idea.
>From an architecture perpective, it mobilise one more piece of software upon
>IMAP SELECT thus harm resiliency.
I'm furthermore in general skeptical with ElasticSearch performance
predictability and operations are often complicated.
> Investigate the use of MessageSearch index for First UNSEEN Uid
> ---------------------------------------------------------------
>
> Key: JAMES-3109
> URL: https://issues.apache.org/jira/browse/JAMES-3109
> Project: James Server
> Issue Type: New Feature
> Components: cassandra, elasticsearch, mailbox
> Reporter: Benoit Tellier
> Priority: Major
>
> After an expunge, or once all emails are read, Cassandra issues tubstone
> range warnings when trying to find first unseen UID of a mailbox reading
> `firstUnseen` table.
> Maybe using the MessageSearch index to get this information is better suited.
> (Directly reused in the Message mapper)
> Scenario:
> - inset 2000 messages in a mailbox
> - Mark them all as Read
> - Insert 10 messages
> - SELECT all unseen
> Regarding mailboxRecent, we also encounter threshold warnings, but I'm
> wondering if this can be treated using the search index as the full list of
> values is expected (but we can try)
> Furthermore relying on the search index will eventually solve coherence issue
> for these tables
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
