[jira] [Resolved] (UNOMI-442) Creating segment with past event condition does not engage correctly existing profiles

["Serge Huber (Jira)" <ji...@apache.org>]

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

Serge Huber resolved UNOMI-442.
-------------------------------
    Resolution: Fixed

> Creating segment with past event condition does not engage correctly existing profiles
> --------------------------------------------------------------------------------------
>
>                 Key: UNOMI-442
>                 URL: https://issues.apache.org/jira/browse/UNOMI-442
>             Project: Apache Unomi
>          Issue Type: Bug
>    Affects Versions: 2.0.0, 1.5.5
>            Reporter: Kevan Jahanshahi
>            Priority: Major
>             Fix For: 2.0.0, 1.5.5
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> When you create a segment definition that contains a past event condition.
>  * first we update all the existing profiles for the past event condition
>  * then we update the profiles for the segment.
> But the second part is not working because the first part is delayed due to the usage of the BulkProcessor.
> So this actions are actually performed in the bad order.
> Proposed fixed: do not use the bulk processor to update profiles for the past event condition. This way the segment update will be able to engage correctly the profile to the segment.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)