[
https://issues.apache.org/jira/browse/UNOMI-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Serge Huber updated UNOMI-462:
------------------------------
Fix Version/s: (was: 1.5.6)
1.5.7
> PastEventCondition generatedPropertyKey count is NOT updated on daily process
> if the profile didn't have events in the date range
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: UNOMI-462
> URL: https://issues.apache.org/jira/browse/UNOMI-462
> Project: Apache Unomi
> Issue Type: Bug
> Components: core
> Affects Versions: 1.5.4
> Reporter: Ben Schiefer
> Priority: Major
> Fix For: 1.5.7
>
>
> SegmentServiceImpl has a daily process that updates the matching event count
> for pastEventConditions
> ([https://github.com/apache/unomi/blob/1e0a8983cabd6f244c26d516c834bf90c0faccde/services/src/main/java/org/apache/unomi/services/impl/segments/SegmentServiceImpl.java#L1125)]
>
> This process generates a query that includes a date range to find matching
> event counts for profiles within a certain window, and then updates the count
> for the generatedPropertyKey on each profile.
> This process works as expected for profiles generating NEW matching events
> within the new date range, but it does NOT update profiles that have not
> generated any new matching events in the new date range.
>
> What I would have expected to see is any profiles that were previously
> assigned the corresponding generatedPropertyKey, but didn't have any new
> events on this daily run, would have the count of that generatedPropertyKey
> set to 0.
> Steps to Reproduce
> 1. Create segment with pastEventCondition, numberOfDays: 1
> 2. Post an event that matches the eventCondition.
> 3. Notice that the profile has a pastEvent count for eventTriggeredxxx: 1,
> and the profile will have the segment created in step 1 assigned to it.
> 4. Wait for the daily process to run so that the previously created event
> would be outside of the 1 day window.
> 5. Notice the profile still has eventTriggeredxxx: 1, and is still a member
> of the segment created in step 1.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
