This is an automated email from the ASF dual-hosted git repository. shuber pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/unomi.git
commit 37e2eefea3a0c42b29b30164bcfa9941463a59fd Merge: f6f4711 325cae3 Author: Serge Huber <[email protected]> AuthorDate: Thu Dec 12 16:59:32 2019 +0100 Merge pull request #121 from apache/UNOMI-225-fix-migration-mappings UNOMI-225 ElasticSearch 7 fix issues with mappings when migrating manual/src/main/asciidoc/new-data-model.adoc | 3 + .../resources/META-INF/cxs/mappings/event.json | 35 +++++ .../resources/META-INF/cxs/mappings/profile.json | 3 + .../resources/META-INF/cxs/mappings/session.json | 26 ++++ .../unomi/shell/migration/impl/MigrationTo150.java | 153 +++++++++++++++++++-- .../unomi/shell/migration/utils/HttpUtils.java | 17 ++- 6 files changed, 219 insertions(+), 18 deletions(-) diff --cc manual/src/main/asciidoc/new-data-model.adoc index 8d39086,ecea896..48d19f5 --- a/manual/src/main/asciidoc/new-data-model.adoc +++ b/manual/src/main/asciidoc/new-data-model.adoc @@@ -92,10 -84,8 +92,13 @@@ Once in the console launch the migratio migrate 1.4.0 Follow the instructions and answer the prompts. If you used the above configuration as an example you can simply use the -default values. Note that it is also possible to change the index prefix to be different from the default `context` value +default values. + +Be careful because the first address that the tool will ask for is the `target` (ElasticSearch 7) cluster, not the +ES 5 one. + +Note that it is also possible to change the index prefix to be different from the default `context` value so that you could host multiple Apache Unomi instances on the same ElasticSearch cluster. + + Important note: only the data that Apache Unomi manages will be migrate. If you have any other data (for example Kibana + or ElasticSearch monitoring indices) they will not be migrated by this migration tool.
