[
https://issues.apache.org/jira/browse/UNOMI-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18095505#comment-18095505
]
Serge Huber commented on UNOMI-614:
-----------------------------------
h2. Re-targeted to unomi-3.2.0
Moved fixVersion from {{unomi-3.1.0}} to {{unomi-3.2.0}}.
Storing human-readable segment names on profiles (alongside segment IDs) is a
reporting convenience. On {{master}}, profiles still store {{segments}} as a
set of segment IDs only. Denormalizing names requires segment rename/rename
propagation rules and ES/OS mapping updates — out of scope for 3.1.0 GA.
h2. Workaround for 3.1
Resolve names at query time (join segment definitions by ID in Kibana, BI, or
via REST {{/cxs/segments}}). Profile CSV export already includes segment names
in export output; that does not change stored profile documents.
> Add segmentNames to profiles
> ----------------------------
>
> Key: UNOMI-614
> URL: https://issues.apache.org/jira/browse/UNOMI-614
> Project: Apache Unomi
> Issue Type: Improvement
> Components: unomi(-core)
> Affects Versions: unomi-2.0.0, unomi-1.6.0
> Reporter: Serge Huber
> Priority: Major
> Fix For: unomi-3.2.0
>
> Attachments: Profile_scopes_&_segment_names1.patch
>
>
> It would be really interesting to have a little more information in Profiles
> to do interesting reporting. Notably: the display names of the segments
> The idea is the following:
> Currently we store the segmentIDs in the profile, but these are not human
> readable and can be confusing when using Kibana reporting or other systems
> that directly access ElasticSearch data. The idea would be to add another
> property that would also store the segmentName in the profile. Another
> alternative solution would be to change the data structure for the segments
> in the profile and use sub-objects such as
> { "segmentID" : "97348258", "segmentName" : "leads" }
> Attached is a prototype that also contains the implementation of another
> ticket as they were done at the same time. See UNOMI-613 for more information.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
