atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shwetha G S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-106) Store createTimestamp and modified timestamp separately for an entity
Date Tue, 22 Dec 2015 12:00:51 GMT

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

Shwetha G S commented on ATLAS-106:
-----------------------------------

{code}
-    public static final String TIMESTAMP_PROPERTY_KEY = INTERNAL_PROPERTY_KEY_PREFIX + "timestamp";
+    public static final String CREATION_TIMESTAMP_PROPERTY_KEY = INTERNAL_PROPERTY_KEY_PREFIX
+ "creationTimestamp";
{code}
Can you keep the create time variable as is for backward compatibility?

In TypedInstanceToGraphMapper.addOrUpdateAttributesAndTraits(), updating modified time should
be done only if the operation is update

We use https://reviews.apache.org/dashboard/ for bigger patches as its easier to add comment
and track updates there. Can you create review board request going forward? Thanks for taking
up this change

> Store createTimestamp and modified timestamp separately for an entity
> ---------------------------------------------------------------------
>
>                 Key: ATLAS-106
>                 URL: https://issues.apache.org/jira/browse/ATLAS-106
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Suma Shivaprasad
>            Assignee: David Kantor
>         Attachments: ATLAS-106-v6.patch
>
>
> Currently we store only the Create timestamp in atlas. Would be better to separate to
track create and modified time separately , in cases where we want to support search queries
give all entities which have been modified in the past 1 day etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message