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. JSON schema. This means object properties must be declared in a JSON schema for an event to be accepted. A new property, flattenedProperties has been introduced to the event object, this property has been

. . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.3.2. Retrieving a context as a JSON object.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . .

they can be affected to. For example, the following Apache Unomi 1.1.x - Documentation - 1 JSON document can be passed to Unomi to declare a new property type identified (and named) tweetNb, tagged with be seen as a sentence, the event’s type being the verb, the source the subject and the target the object. Event structure: { "eventType": , "scope": , progressively builds a picture of who the user is and how they behave. This knowledge is embedded in Profile object. A profile is an Item with any number of properties and optional segments and scores. Unomi provides