This is an automated email from the ASF dual-hosted git repository. btellier pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/james-project.git
commit 14051e0ce3e37d7c075819d431e417b1f034ee40 Author: Benoit Tellier <[email protected]> AuthorDate: Wed May 29 10:01:28 2019 +0700 JAMES-2766 ElasticSearch 6 upgrade: Document port configuration changes ElasticSearch 6 driver is relying on the high-level REST client and no more on the internal transport protocol. Thus, you need to update your configuration files accordingly: In `elasticsearch.properties` modify the `elasticsearch.port` properties to reference the HTTP port of your ElasticSearch nodes (**9200** by default instead of the previous default value of **9300**). --- upgrade-instructions.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/upgrade-instructions.md b/upgrade-instructions.md index 4399a14..88708d5 100644 --- a/upgrade-instructions.md +++ b/upgrade-instructions.md @@ -33,6 +33,15 @@ In version 3.3.0 indexing for the Cassandra product was handled using ElasticSea Note that ElasticSearch APIs had been undergoing some major changes, making a smooth migration hard to provide. We proposed 2 migration strategies. A simple one leading to major search inconsistencies in the process, and another one mitigating these inconsistencies (but getting rid of them). +#### Configuration changes + +ElasticSearch 6 driver is relying on the high-level REST client and no more on the internal transport protocol. + +Thus, you need to update your configuration files accordingly: + +In `elasticsearch.properties` modify the `elasticsearch.port` properties to reference the HTTP port of your ElasticSearch +nodes (**9200** by default instead of the previous default value of **9300**). + ##### Simple strategy Procedure: --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
