You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Jonathan Sinovassin-Naïk (Jira)" <ji...@apache.org> on 2022/08/26 08:29:00 UTC
[jira] [Resolved] (UNOMI-623) Store original event id and event type inside session
[ https://issues.apache.org/jira/browse/UNOMI-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Sinovassin-Naïk resolved UNOMI-623.
--------------------------------------------
Resolution: Fixed
The new fields will be originEventTypes and originEventIds and will contain the types and ids of the events which have been sent when the session has been created.
It's a list of values because, it's possible that there is several events when a session is created
> Store original event id and event type inside session
> -----------------------------------------------------
>
> Key: UNOMI-623
> URL: https://issues.apache.org/jira/browse/UNOMI-623
> Project: Apache Unomi
> Issue Type: Improvement
> Reporter: romain.gauthier
> Assignee: Jonathan Sinovassin-Naïk
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Unomi has some behaviours that are hard to guess regarding session creation.
> To be able to identify why and when new sessions are created, it would be great to add the id of the event that triggered the session creation and its event type.
> I suggest that we create new fields orginEventId and originEventType in the session, maybe in the source?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)