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
The following commit(s) were added to refs/heads/master by this push:
new bdb014b JAMES-3516 Update upgrade instructions follow adding threadId
to ElasticSearch breaking change (#547)
bdb014b is described below
commit bdb014b5c9dbe4939774faf69402297d496c2b48
Author: Trần Hồng Quân <[email protected]>
AuthorDate: Thu Jul 22 18:18:23 2021 +0700
JAMES-3516 Update upgrade instructions follow adding threadId to
ElasticSearch breaking change (#547)
---
upgrade-instructions.md | 27 ++++++++++++++++++++++++++-
1 file changed, 26 insertions(+), 1 deletion(-)
diff --git a/upgrade-instructions.md b/upgrade-instructions.md
index f32ffb4..97bed20 100644
--- a/upgrade-instructions.md
+++ b/upgrade-instructions.md
@@ -15,8 +15,33 @@ Note: this section is in progress. It will be updated during
all the development
Changes to apply between 3.6.x and 3.7.x will be reported here.
Change list:
-
+ - [Adding the threadId to the ElasticSearch
index](#adding-the-threadid-to-the-elasticsearch-index)
- [Rework message denormalization](#rework-message-denormalization)
+ - [Adding threadId column to message metadata
tables](#adding-threadid-column-to-message-metadata-tables)
+
+### Adding the threadId to the ElasticSearch index
+
+Date 22/07/2021
+
+JIRA: https://issues.apache.org/jira/browse/JAMES-3516
+
+Concerned product: Distributed James
+
+Add threadId to James document mapping to enable thread query search.
+
+We already have this field as part of newly created mappings, but we need to
explicitly add this field to existing indices by doing:
+```
+curl -X PUT \
+ http://ip:ESport/mailbox_v1/_mapping \
+ -H 'Content-Type: application/json' \
+ -d '{
+ "properties": {
+ "threadId": {
+ "type": "keyword"
+ }
+ }
+}'
+```
### Rework message denormalization
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
