You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Don Hinshaw (JIRA)" <ji...@apache.org> on 2017/10/26 15:20:00 UTC
[jira] [Updated] (UNOMI-132) ProfileServiceImpl mergeProfiles for
nested profile properties
[ https://issues.apache.org/jira/browse/UNOMI-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Don Hinshaw updated UNOMI-132:
------------------------------
Description:
When merging profiles unomi does not look for profile properties that are nested.
"properties": {
"nbOfVisits": 1,
"lastVisit": "2017-10-25T20:04:49Z",
"group": {
"user_ids": {
"site_1": "123_user_id"
}
},
"firstVisit": "2017-10-25T20:04:49Z",
}
When this profile gets merged, unomi looks for the properties on line 458 in ProfileServiceImpl.
allProfileProperties.addAll(profile.getProperties().keySet());
The keySet() will only include "group", not the values nested inside. So we cannot define a mergeRule for the values inside.
How can we merge two profiles with different user_id values?
Current work around is to use group_user-id_site-1 : "123_user_id" instead of the nested property.
Any thoughts or is this a new use case?
Thanks,
Donnie
was:
When merging profiles unomi does not look for profile properties that are nested.
{{ "properties": {
"nbOfVisits": 1,
"lastVisit": "2017-10-25T20:04:49Z",
"group": {
"user_ids": {
"site_1": "123_user_id"
}
},
"firstVisit": "2017-10-25T20:04:49Z",
}t}}
When this profile gets merged, unomi looks for the properties on line 458 in ProfileServiceImpl.
allProfileProperties.addAll(profile.getProperties().keySet());
The keySet() will only include "group", not the values nested inside. So we cannot define a mergeRule for the values inside.
How can we merge two profiles with different user_id values?
Current work around is to use group_user-id_site-1 : "123_user_id" instead of the nested property.
Any thoughts or is this a new use case?
Thanks,
Donnie
> ProfileServiceImpl mergeProfiles for nested profile properties
> --------------------------------------------------------------
>
> Key: UNOMI-132
> URL: https://issues.apache.org/jira/browse/UNOMI-132
> Project: Apache Unomi
> Issue Type: Wish
> Reporter: Don Hinshaw
> Priority: Minor
>
> When merging profiles unomi does not look for profile properties that are nested.
> "properties": {
> "nbOfVisits": 1,
> "lastVisit": "2017-10-25T20:04:49Z",
> "group": {
> "user_ids": {
> "site_1": "123_user_id"
> }
> },
> "firstVisit": "2017-10-25T20:04:49Z",
> }
> When this profile gets merged, unomi looks for the properties on line 458 in ProfileServiceImpl.
> allProfileProperties.addAll(profile.getProperties().keySet());
> The keySet() will only include "group", not the values nested inside. So we cannot define a mergeRule for the values inside.
> How can we merge two profiles with different user_id values?
> Current work around is to use group_user-id_site-1 : "123_user_id" instead of the nested property.
> Any thoughts or is this a new use case?
> Thanks,
> Donnie
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)