migration/scripts \ --v /home/unomi/migration/assets/:/tmp/assets/ \ apache/unomi:2.0.0-SNAPSHOT Once your cluster is shutdown, performing the migration will be as simple as starting a dedicated perform a full cluster backup/snapshot of the source clusters (including ElasticSearch and Unomi clusters), and ideally to perform the migration on a restored snapshot of the source cluster. For more samples/tweet-button-plugin mvn clean install cp target/tweet-button-plugin-2.0.0-SNAPSHOT.jar ../../package/target/unomi-2.0.0-SNAPSHOT/deploy is displayed. We will now explain in greater details some concepts

following KAR to the Karaf deploy directory, as in this example line: cp kar/target/unomi-kar-1.0.0-SNAPSHOT.kar ~/java/deployments/unomi/apache-karaf-3.0.1/deploy/ . If all went smoothly, you should directory it was created: cp target/tweet-button-plugin-1.0.0-incubating-SNAPSHOT.jar ../../package/target/unomi-1.0.0- incubating-SNAPSHOT/deploy TESTING THE SAMPLE You can now go to http://localhost:8181/index

the target (ElasticSearch 7) cluster It is HIGHLY RECOMMENDED to perform a full cluster backup/snapshot of the source cluster, and ideally to perform the migration on a restore of the source cluster archive in the directory it was created: cp target/tweet-button-plugin-1.5.1-SNAPSHOT.jar ../../package/target/unomi-1.5.1-SNAPSHOT/deploy TESTING THE SAMPLES You can now go to http://localhost:8181/twitter/index definitions from bundles. By default existing definitions will not be overriden unless they come from SNAPSHOT bundles. Using this command you can override this mechanism. Here are some examples of using