You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Luc DUZAN (JIRA)" <se...@james.apache.org> on 2017/06/28 15:01:00 UTC

[jira] [Commented] (JAMES-2071) Improve ElasticSearch mapping

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

Luc DUZAN commented on JAMES-2071:
----------------------------------

The investigation has been done and needed work as been explained in the following ticket:
* https://issues.apache.org/jira/browse/JAMES-2078
* https://issues.apache.org/jira/browse/JAMES-2079
* https://issues.apache.org/jira/browse/JAMES-2080


> Improve ElasticSearch mapping
> -----------------------------
>
>                 Key: JAMES-2071
>                 URL: https://issues.apache.org/jira/browse/JAMES-2071
>             Project: James Server
>          Issue Type: Improvement
>            Reporter: Luc DUZAN
>
> Firstly in a first time, we put header in ES but we do not specify anything about them in the mapping!
> By default each time ES see a field (or "subfield") it infear the type for it and create a index for it. If a new document arrive with the same field with a type that is different from the inferre type that will create a exception.
> So in a first time we should specify in the mapping all the header we need to look for and move the mapping to `dynamic: false`.
> Also we should review the mapping to see if it suffers from other issues.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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