introduction of tighter data validation with JSON Schemas required some changes in the product data model, which presented an opportunity for noticeable improvements in the overall performance. This new corresponding section of the documentation. 1.1.4. UPDATED DATA MODEL The introduction of JSON schema required us to modify Apache Unomi data model, One of the key differences is the removal of open maps. following in Apache Unomi 2.x: If using the default Apache 1.x data model, our Unomi 2 migration process will handle the data model changes for you. If you are using custom events/objects, please refer

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 8.1. Data Model Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 8.19. Data Model changes for Apache Unomi 1.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 8.19.1. Data model and ElasticSearch 7 . . . \ --user karaf:karaf \ --form 'file=@hello-world.groovy' Finally, register a rule to trigger execution of the groovy action: Apache Unomi 1.x - Documentation - 33 curl -X POST 'http://localhost:8181/cxs/rules'