atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Kantor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-106) Store createTimestamp and modified timestamp separately for an entity
Date Mon, 14 Dec 2015 14:55:46 GMT

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

David Kantor commented on ATLAS-106:
------------------------------------

[~suma.shivaprasad] Kindly review the updated patch at your earliest convenience and let me
know if there any further issues.  I am working on ATLAS-122 which affects some of the same
files changed in ATLAS-106, and I am very close to submitting a patch for ATLAS-122.  So I
would like to resolve ATLAS-106 before submitting ATLAS-122.

> 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-v1.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