[
https://issues.apache.org/jira/browse/UNOMI-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17341944#comment-17341944
]
Amit Cohen commented on UNOMI-482:
----------------------------------
Thanks for answering.
the solution you suggested could cause breaking changes for users that want the
event.timestamp no matter what.
Again - for a “clean” system I think “now” should be the real now (Date()), and
maybe “eventTime” for event.timestamp
but we cannot do this without causing these breaking changes.
I think Unomi should support the real now this way or another
> 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
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
