[
https://issues.apache.org/jira/browse/JAMES-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-2769.
---------------------------------
Resolution: Fixed
This is done, dynamic indexing had been turned off in ElasticSearch mapping
accordingly.
but the big catch is that we now rely on NESTED elements to represent headers
which have performance implications.
> Indexing a header should default on a defined type
> --------------------------------------------------
>
> Key: JAMES-2769
> URL: https://issues.apache.org/jira/browse/JAMES-2769
> Project: James Server
> Issue Type: New Feature
> Components: elasticsearch
> Reporter: Raphael Ouazana
> Priority: Major
>
> When indexing an email, each header define a new index. If a header is
> detected as being a date in a first email, it will be created as a date,
> while it could contain other data.
> Because of that, an other email with same header but other data won't be
> indexed.
> See here for a more detailed report:
> https://github.com/linagora/openpaas-esn/issues/61
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
