[
https://issues.apache.org/jira/browse/UNOMI-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevan Jahanshahi updated UNOMI-522:
-----------------------------------
Fix Version/s: unomi-2.0.0
> EventCollector saving temporary profiles
> ----------------------------------------
>
> Key: UNOMI-522
> URL: https://issues.apache.org/jira/browse/UNOMI-522
> Project: Apache Unomi
> Issue Type: Bug
> Components: unomi(-core)
> Affects Versions: unomi-1.4.0, unomi-1.5.7
> Reporter: Kevan Jahanshahi
> Assignee: Kevan Jahanshahi
> Priority: Major
> Fix For: unomi-2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> There is issues with profile handling in the EventCollector.
> * In case you send an event that will update the profile, like a login event.
> * on a new session ID
> * with no profile already known by unomi
> * EventCollector is creating a temporary profile, prefixed by: "temp_"
> * normally, this kind of profile should not persisted, but in case the event
> sent trigger rules and actions that will modify the profile (that is new),
> then the profile will be saved with the temporary id prefixed by "temp_"
> I think the profile creation handling in the event collector is really bad,
> and should no deal with temporary id.
> The question is not easy to answer, does the event collector should do the
> same as context.js ?
> * create the profile
> * send the profile id in the cookie ?
> May be event collector should not be used to create profile, but then how can
> we control this ?
> Anyway we should not persist this temporary profile.
> It can be dangerous with the profile merge, because user can get this
> temporary profile assigned to them.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
