Jonathan Sinovassin-Naïk created UNOMI-859:
----------------------------------------------
Summary: Improve eventCollector response
Key: UNOMI-859
URL: https://issues.apache.org/jira/browse/UNOMI-859
Project: Apache Unomi
Issue Type: Bug
Reporter: Jonathan Sinovassin-Naïk
When calling the eventCollector request, we don't know exactly what happens.
The response to the request only provides information regarding the profile or
session update, with the following codes:
4: PROFILE_UPDATED (Profile updated)
6: SESSION_UPDATED (Session updated)
0: NO_CHANGES (No changes)
1: ERROR (Error)
However, several specific cases return the same response:
If an event is rejected due to third-party configuration, the response is
{"updated": 0}.
If the current profile is not updated during the call, the response is also
{"updated": 0}.
If a profile other than the current user's profile is updated, the response
will still be {"updated": 0}.
This creates ambiguity because it becomes impossible to distinguish between:
A rejected event,
No profile update,
A profile update for someone other than the current user.
We should include more information in the response to clarify what is happening
during the call.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
