You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Aneesha Kaushal (Jira)" <ji...@apache.org> on 2023/01/30 11:05:00 UTC

[jira] [Commented] (UNOMI-420) mergeProfileOnPropertyAction - support updates of mergeIdentifier

    [ https://issues.apache.org/jira/browse/UNOMI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682014#comment-17682014 ] 

Aneesha Kaushal commented on UNOMI-420:
---------------------------------------

In case we have multiple profile properties set as merge properties eg: the user's id and the user's email then flag `forceEventProfileAsMaster` results in overcounting of profile properties. I have a case when two profiles have orders(2,3 respectively) and they are merged with 3 merge identifiers. When these profiles are merged then it results in 9 orders rather than 5.  
```
profile1 has orders as 2
profile2 with order as 3
While merging- 2(profile1.orders)3(since 3 identifiers are there) + 3 (profile2.orders) = (2*3)+3 = 9
```

> mergeProfileOnPropertyAction - support updates of mergeIdentifier
> -----------------------------------------------------------------
>
>                 Key: UNOMI-420
>                 URL: https://issues.apache.org/jira/browse/UNOMI-420
>             Project: Apache Unomi
>          Issue Type: Improvement
>            Reporter: Gilad W
>            Priority: Major
>             Fix For: unomi-1.5.5
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> when flaged asĀ forceEventProfileAsMaster, and profile merge identifier has been changed.
> support updating the existing "masterProfile" instead of creating a new profile



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