[
https://issues.apache.org/jira/browse/UNOMI-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17339655#comment-17339655
]
Serge Huber commented on UNOMI-482:
-----------------------------------
Again this is only true if the event is provided with an external timestamp
which in most cases is not the usual usage.
Maybe we could instead check if the timestamp is older than the current system
time and change the behavior of the "now" in this case as well as the
lastUpdatedTime. Also I could see some scenarios where it could be interesting
to have the lastUpdateTime set to the event timestamp in the past (data
migration or copy scenarios).
> SetPropertyAction eventArrivalTime
> ----------------------------------
>
> Key: UNOMI-482
> URL: https://issues.apache.org/jira/browse/UNOMI-482
> Project: Apache Unomi
> Issue Type: New Feature
> Reporter: Amit Cohen
> Priority: Major
>
> In setPropertyAction, "now" in propertyValue is being translated to
> event.timeStamp.
> I would like to add support for "eventArrivalTime" which will be the current
> time in which the event got into Unomi.
> an example to emphasize the need -
> event1 arrived with timestamp - 8:00
> then, event2 arrived with timestamp - 7:00
> the profile will be updated with lastUpdatedTime - 7:00, which is not true
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
