[
https://issues.apache.org/jira/browse/FALCON-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055556#comment-15055556
]
Ajay Yadava commented on FALCON-1661:
-------------------------------------
[~peeyushb] What is the problem that you are facing because of timestamp not
being different? Are these same nominal times or same actual times? I will
expect timestamp to contain nominal time and not actual time(we may add it in
separate property). Reason for this is that the nominal time of the coordinator
is predictable and unique, while the actual time/current time is not, so it
will loose it's relevance for querying for instances in a time range.
> 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)
