falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "pavan kumar kolamuri (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1661) Similar timestamp is getting added for Falcon instance vertex in GraphDB
Date Tue, 15 Dec 2015 08:21:46 GMT

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

pavan kumar kolamuri commented on FALCON-1661:
----------------------------------------------

[~peeyushb] I agree for your case , but in graph db we should always store nominal time of
instances and as [~ajayyadava] mentioned we can store timestamp also as additional column,
 it can be current time when instance added. Based on use cases user's will sort . But in
general scenario we should always store nominal time which will be useful for querying.

> Similar timestamp is getting added for Falcon instance vertex in GraphDB
> ------------------------------------------------------------------------
>
>                 Key: FALCON-1661
>                 URL: https://issues.apache.org/jira/browse/FALCON-1661
>             Project: Falcon
>          Issue Type: Bug
>          Components: common
>            Reporter: Peeyush Bishnoi
>            Assignee: Peeyush Bishnoi
>             Fix For: 0.9
>
>
> When working on FALCON-1643, I found that same "timestamp" is getting set upon adding
Falcon instances vertices in GraphDB. Due to this while trying to sort the vertices on timestamp
many instances are not getting sorted properly.



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

Mime
View raw message