[
https://issues.apache.org/jira/browse/UNOMI-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17111087#comment-17111087
]
Noa commented on UNOMI-338:
---------------------------
First event's cURL:
curl --location --request POST 'http://localhost:8181/context.json' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic a2FyYWY6a2FyYWY=' \
--header 'Content-Type: text/plain' \
--data-raw '{
"sessionId": "session1",
"events": [
{
"eventType":"type1",
"properties" : {
"source": "root",
"email" : "[email protected]"
}
}
]
}'
> Profile's "lastVisit" and "firstVisit" are not calculated properly
> ------------------------------------------------------------------
>
> Key: UNOMI-338
> URL: https://issues.apache.org/jira/browse/UNOMI-338
> Project: Apache Unomi
> Issue Type: Bug
> Components: core
> Reporter: Noa
> Priority: Minor
> Attachments: Screen Shot 2020-05-19 at 13.28.52.png
>
>
> The profile's "lastVisit" and "firstVisit" properties doesn't take into
> consideration that an event can be added with a custom timestamp.
> This can cause an OLD event to be considered as the "lastVisit" and a NEWER
> event as the "firstVisit".
> I attached a screenshot for an example -
> lastVisit -> April 18th
> firstVisit -> May 19th
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
