[
https://issues.apache.org/jira/browse/MAILBOX-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit resolved MAILBOX-266.
------------------------------------
Resolution: Fixed
I took the specified step.
We implemented the DeleteByQuery ourselves (to have control on the task)
We added some unit tests and corrected problems on sorts, user flags, and some
date resolution conversion.
Finally, we added a scroll for the search
Now, we uses a single ElasticSearch client for the whole James server.
> Rely on last ElasticSearch version (2.2.1)
> ------------------------------------------
>
> Key: MAILBOX-266
> URL: https://issues.apache.org/jira/browse/MAILBOX-266
> Project: James Mailbox
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Tellier Benoit
> Fix For: 0.6
>
>
> We should update ElasticSearch version before release 3.0.
> Main changes are :
> - Filter deprecation : instead a filter parameter is added to BoolQueries
> - Store memory do not exists anymore
> - DeleteByQuery as been removed
> - Some other minor changes in the java API
> So :
> - We need to rework query conversion. The code is simpler with only
> BoolQueries
> - We should use a temporary folder for ElasticSearch content
> - I concider installing the DeleteByQuery plugin.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
