[prev in list] [next in list] [prev in thread] [next in thread] 

List:       james-dev
Subject:    [jira] [Commented] (MAILBOX-258) MailboxRenamed event not handled by ListeningMessageSearchIndex
From:       "ASF GitHub Bot (JIRA)" <jira () apache ! org>
Date:       2015-11-28 13:25:11
Message-ID: JIRA.12909400.1446290450000.213795.1448717111063 () Atlassian ! JIRA
[Download RAW message or body]


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

ASF GitHub Bot commented on MAILBOX-258:
----------------------------------------

Github user chibenwa closed the pull request at:

    https://github.com/apache/james-project/pull/14


> MailboxRenamed event not handled by ListeningMessageSearchIndex
> ---------------------------------------------------------------
> 
> Key: MAILBOX-258
> URL: https://issues.apache.org/jira/browse/MAILBOX-258
> Project: James Mailbox
> Issue Type: Bug
> Components: lucene
> Affects Versions: 0.6
> Reporter: Tellier Benoit
> Fix For: 0.6
> 
> 
> This means that renaming a mailbox is not handled by the search index.
> ListeningMessageSearch should listen to MailboxRenamed events, and handle an update \
> for all concerned documents concerning their mailbox. Concerning elasticsearch, it \
> might be complicated to implement as their is not yet an UpdateByQuery API :-( An \
> explicit call to the ReIndexer will do the trick... Do you consider this acceptable \
> ? Any better idea ?  Note : we can't iterate on message range (2^64 values for \
> MessageRange::all() ) to update documents one by one....



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


[prev in list] [next in list] [prev in thread] [next in thread]