james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Charles (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAILBOX-186) Missing indices on JPA mailstore database results in poor mailbox listing as the number of messages grows
Date Sun, 25 Nov 2012 12:38:58 GMT

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

Eric Charles commented on MAILBOX-186:
--------------------------------------

I have added @Index on line attribute which works fine, and also attempted to define an index
on multiple columns which is fails due to OPENJPA-223.
I have added a comment to OPENJPA-223 to see if someone has a workaround or a fix.

(see commit http://svn.apache.org/viewvc?rev=1413343&view=rev)

Thx Craig for reporting. We need to let this open and in the meantime, create the index on
the 2 columns manually.
                
> Missing indices on JPA mailstore database results in poor mailbox listing as the number
of messages grows
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: MAILBOX-186
>                 URL: https://issues.apache.org/jira/browse/MAILBOX-186
>             Project: James Mailbox
>          Issue Type: Bug
>          Components: jpa
>    Affects Versions: 0.4
>            Reporter: Craig George
>
> We have an application which queries the IMAP store of Apache James 3 in the following
manner:
> final Message[] messages = this.folder.getMessages();
> final FetchProfile fetchProfile = new FetchProfile();
> fetchProfile.add(Item.ENVELOPE);
> fetchProfile.add(Item.FLAGS);
> fetchProfile.add(Item.CONTENT_INFO);
> fetchProfile.add(IMAPFolder.FetchProfileItem.HEADERS);
> fetchProfile.add(IMAPFolder.FetchProfileItem.SIZE);
> fetchProfile.add(UIDFolder.FetchProfileItem.UID);
> this.folder.fetch(messages, fetchProfile);
> When this query is performed on a folder with a large number of messages the response
times degrade very quickly. This is due to the following query being run *for each* message:
> SELECT t0.PROPERTY_ID,
>     t0.PROPERTY_LINE_NUMBER,
>     t0.PROPERTY_LOCAL_NAME,
>     t0.PROPERTY_NAME_SPACE,
>     t0.PROPERTY_VALUE
> FROM MA_DIRECT_APACHE_JAMES.JAMES_MAIL_PROPERTY t0
> WHERE t0.MAILBOX_ID = :1
> AND t0.MAIL_UID = :2
> ORDER BY t0.PROPERTY_LINE_NUMBER ASC
> The problem is that in the JAMES_MAIL_PROPERTY table only the PROPERTY_LINE_ID column
is indexed, implicity by virtue of the fact that it is the primary key. The workaround is
to add the following indexes on the table:
> CREATE INDEX I_JMS_MIL_PROPERTY_MSG_ID ON JAMES_MAIL_PROPERTY (MAILBOX_ID, MAIL_UID);
> CREATE INDEX I_JMS_MIL_PROPERTY_LINE_NUMBER ON JAMES_MAIL_PROPERTY (PROPERTY_LINE_NUMBER);

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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


Mime
View raw message