[
https://issues.apache.org/jira/browse/JAMES-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17254718#comment-17254718
]
Benoit Tellier commented on JAMES-2037:
---------------------------------------
The above ticket provided an efficient way to list UIDs inside a mailbox.
We found out that some IMAP clients perform a Search by uid
1:9223372036854775807 (min to max) to resynchronize themselves.
As such, like LIST_ALL_QUERY, it should be resolved against primary storage,
using efficient UID listing APIs implemented above..
IMAP logs:
{code:java}
SearchOperation{key=SearchKey{type=TYPE_UID, date=null, size=0, value=null,
seconds=-1, modSeq=-1, uids=[IdRange : TYPE: FROM UID:
MessageUid{uid=1}:MessageUid{uid=9223372036854775807}], sequences=null,
keys=Optional.empty}, options=[]}
{code}
> Avoid reading messages when building UID <=> MSN mapping upon SELECT
> --------------------------------------------------------------------
>
> Key: JAMES-2037
> URL: https://issues.apache.org/jira/browse/JAMES-2037
> Project: James Server
> Issue Type: Improvement
> Components: IMAPServer
> Reporter: Benoit Tellier
> Priority: Major
>
> SelectedMailboxImpl builds the UID <=> MSN mapping for later uses.
> Today, to do so, we read messages, and keep their UID.
> Needless to say, for some back-ends reading messages is an expensive
> operation requiring "soft joins" (Cassandra). We should offer a way to
> directly get an Iterator of UIDs in the mailbox.
> That would allow further optimizations, mostly on Cassandra implementations,
> avoid thousands of queries upon IMAP SELECT commands on large mailboxes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
