You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "romain.gauthier (Jira)" <ji...@apache.org> on 2022/01/10 10:02:00 UTC

[jira] [Created] (UNOMI-544) Simplify personalization requests resolution by using internal events

romain.gauthier created UNOMI-544:
-------------------------------------

             Summary: Simplify personalization requests resolution by using internal events
                 Key: UNOMI-544
                 URL: https://issues.apache.org/jira/browse/UNOMI-544
             Project: Apache Unomi
          Issue Type: Improvement
            Reporter: romain.gauthier
             Fix For: 1.6.0


In Unomi, personalization requests are currently not considered as events.

Changing the way personalization requests are managed, and considering them just as any other event would have several benefits: 
 * Remove some custom code
 * Make it easier to understand personalizations when developers start with Unomi
 * Improve code related to event processing, that would apply to all events and make the system more powerful 

 

In this ticket: 
 * a new type of event should be created "personalizationRequest" for instance.
 * to ensure retro compatibility, context.json endpoint should be updated to create the personalizationRequest event internally 
 * Custom code related to personalization management should be removed 
 * integration test should be created or updated to support personalizationRequest
 * Response of the personalization request should be managed, either:
 ** by passing the results as events attributes
 ** OR by updating the personalization request event
 ** OR by improving more globally the way event results can be passed to the original endpoint 

 

Note: 

In Unomi 2.0, some code related to filters should be deprecated. 

 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)