COMPATIBILITY Starting with version 1.5.0 Apache Unomi adds compatibility with ElasticSearch 7.4 . It is highly recommended to use the ElasticSearch version provided by the documentation when possible. However to requests. You can then open a browser and go to http://localhost:8181/cxs to see the list of available RESTful services or retrieve an initial context at http://localhost:8181/context.json (which isn’t be retrieved. In this case we use the wildcard character '*' to say we want to retrieve all the available properties. The structure of the JSON object that you should send is a JSON- serialized version

and/or schemas extensions to be registered. More details about JSON Schemas implementation are available in the corresponding section of the documentation. 1.1.4. UPDATED DATA MODEL The introduction GraphQL API. Available behind a feature flag (the API disabled by default), the GraphQL API is available for you to play with. More details about how to enable/disable the GraphQL API are available in the scripts can only handle objects we know of. More details about migration (incl. of custom events) is available in the corresponding section corresponding section of the documentation. 1.1.8. ELASTICSEARCH

defining new types, users specify which properties (including the type of values they accept) are available to items of that specific type. Unomi defines default value types: date, email, integer and string applications. For this reason, data collected for a given profile in a specific scope is still available to any scoped item that accesses the profile information. It is interesting to note that there across applications and different observation contexts. As identifying information might not be available in all contexts in which data is collected, resolving profiles to a single physical user can become