[jira] [Assigned] (UNOMI-817) past event conditions can generate mapping explosions

["Jonathan Sinovassin-Naïk (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/UNOMI-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Sinovassin-Naïk reassigned UNOMI-817:
----------------------------------------------

    Assignee: Jonathan Sinovassin-Naïk

> past event conditions can generate mapping explosions
> -----------------------------------------------------
>
>                 Key: UNOMI-817
>                 URL: https://issues.apache.org/jira/browse/UNOMI-817
>             Project: Apache Unomi
>          Issue Type: Improvement
>            Reporter: Romain Gauthier
>            Assignee: Jonathan Sinovassin-Naïk
>            Priority: Major
>             Fix For: unomi-2.5.0
>
>
> For past event conditions, we add a property \{{eventTriggered+md5}} to the profile and session indexes.
> But these properties are never cleaned even if the th condition doesn't exist anymore.
> This can result in a large number of properties getting added to the index, and could lead to a mapping explosion.
> Tech notes: 
>  * These properties need to be moved to a nested or flattened property (ensure it performs well and that each eventTrigger doesn't NOT create a new mapping, we need only one mappping for all eventTriggered)
>  * pastEventQueryBuilder, pastEventConditionEvaluator, setEventOccurenceCount action need to be updated 
>  * If there is a way to prevent these properties to be copied to the session, that would be great
>  * Requires a migration script, including a full reindexation of the profiles to clean previous mappings 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)