[
https://issues.apache.org/jira/browse/UNOMI-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevan Jahanshahi updated UNOMI-691:
-----------------------------------
Affects Version/s: unomi-1.7.0
unomi-2.1.0
unomi-1.8.0
> Control groups dont work well with profile merge
> ------------------------------------------------
>
> Key: UNOMI-691
> URL: https://issues.apache.org/jira/browse/UNOMI-691
> Project: Apache Unomi
> Issue Type: Bug
> Affects Versions: unomi-1.7.0, unomi-2.1.0, unomi-1.8.0
> Reporter: romain.gauthier
> Assignee: Kevan Jahanshahi
> Priority: Major
> Fix For: unomi-2.2.0, unomi-1.8.0, unomi-1.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> h3. Context:
> - The control groups are currently stored as a list, inside a profile or
> session property, depending on the control group configuration
> - On login or any other profile stitching event, properties values are
> usually merged
> h3. Problem:
> Assuming https://issues.apache.org/jira/browse/UNOMI-690 has been fixed
> h4. Given there are 2 profiles
> - A, anonymous profile, with control group 123=true, 234=false, 456=missing
> - B, identified profile, belonging to control group 123=false, 234=missing,
> 456=true
> h4. Observed behavior
> On profile merge, A will either erase all control groups of B
> h4. Expected behavior
> On profile merge, control groups for profile B should switch from:
> 123=false, 234=missing, 456=true
> to:
> 123=false, 234=false, 456=true
> In other words, I think that merging of control groups should use some kind
> of custom "set if missing" strategy for each control group value inside the
> list.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
