You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Peeyush Bishnoi (JIRA)" <ji...@apache.org> on 2015/12/13 11:20:46 UTC
[jira] [Commented] (FALCON-1661) Similar timestamp is getting added
for Falcon instance vertex in GraphDB
[ https://issues.apache.org/jira/browse/FALCON-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054900#comment-15054900 ]
Peeyush Bishnoi commented on FALCON-1661:
-----------------------------------------
On debugging this issue, I found that same "timestamp" is getting set upon adding vertex because Falcon instance vertex "timestamp" is based on Oozie coordinator actual time.
{code:java}
name=hdfs-replication/2015-12-12T03:20Z type=PROCESS_INSTANCE timestamp=1449890580000
name=hdfs-replication/2015-12-13T03:25Z type=PROCESS_INSTANCE timestamp=1449890880000
name=hdfs-replication/2015-12-13T03:30Z type=PROCESS_INSTANCE timestamp=1449890880000
name=hdfs-replication/2015-12-13T03:35Z type=PROCESS_INSTANCE timestamp=1449890880000
{code}
I think that "timestamp" of each added instance vertex should be unique.
Thoughts please.
> 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)