dynamic properties. If there is dynamic properties that you want to send with your event, you should use the flattenedProperties field of the event. It’s also necessary to specify the format of the values vulnerabilities (fixed in Elasticsearch 7.16.3). This version increase is releated to Apache Unomi 2.0 makeing use of a new Elasticsearch field type called Flattened (https://www.elastic.co/guide/en/elasticsearch/reference/7 https://www.elastic.co/downloads/past-releases/elasticsearch-7-17-5 (please make sure you use the proper version : 7.17.5) 3) Uncompress it and change the config/elasticsearch.yml to include

https://www.elastic.co/downloads/past-releases/elasticsearch-7-4-2 (please make sure you use the proper version : 7.4.2) 3) Uncompress it and change the config/elasticsearch.yml to include the so you should use them at your own risks. ELASTICSEARCH COMPATIBILITY Starting with version 1.5.0 Apache Unomi adds compatibility with ElasticSearch 7.4 . It is highly recommended to use the ElasticSearch es are properties that take an array of property names that should be retrieved. In this case we use the wildcard character '*' to say we want to retrieve all the available properties. The structure

"profiles", "type": "integer" } Unomi defines a built-in scope (called systemscope) that clients can use to share data across scopes. 1.1.2. EVENTS Users' actions are conveyed from clients to the context install -P generate-package The Maven build process will generate both a standalone package you can use directly to start the context server (see "Deploying the generated package") or a KAR file that you an existing Karaf server") If you want to build and run the integration tests, you should instead use : mvn -P integration-tests clean install 2.1.1. DEPLOYING THE GENERATED PACKAGE The "package" sub-project