You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Serge Huber (Jira)" <ji...@apache.org> on 2022/06/20 13:04:00 UTC

[jira] [Commented] (UNOMI-601) TimeStamp for Metadata class

    [ https://issues.apache.org/jira/browse/UNOMI-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17556366#comment-17556366 ] 

Serge Huber commented on UNOMI-601:
-----------------------------------

Hello, 

Thank you for your contribution. I actually had in mind that we would need more metadata for more (all) objects and was thinking we should add something like this:

New fields:
created : Date
creationVendor : String
creationScope : String (null if provided by vendor)
updated : Date
updateVendor : String
updateScope : String

This way we could distinguish updates from creation and also know which scope performed what. However this requires more management of the values from an implementation point of view. Would you be interested in contributing something like this as currently I don't have the bandwidth to work on it?



> TimeStamp for Metadata class
> ----------------------------
>
>                 Key: UNOMI-601
>                 URL: https://issues.apache.org/jira/browse/UNOMI-601
>             Project: Apache Unomi
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.6.0
>            Reporter: Saad Mairaj
>            Priority: Major
>             Fix For: 2.0.0, 1.6.1
>
>   Original Estimate: 1h
>          Time Spent: 10m
>  Remaining Estimate: 50m
>
> It gets challenging to sort and manage documents like segments, campaigns, lists, goals & rules as the timestamp field is missing. Adding an extra field timeStamp to metadata will give a timestamp field for all the documents other than profiles, sessions & events.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)