[
https://issues.apache.org/jira/browse/FALCON-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057482#comment-15057482
]
Peeyush Bishnoi commented on FALCON-1661:
-----------------------------------------
[~ajayyadava] As I have already mentioned, presently in GraphDB when vertex get
added it has a "timestamp" on the basis of Oozie coordinator actual
time/created time but not on the nominal time. I require to do sorting on
"timestamp", and ordering of vertices is not coming proper as many vertices
"timstamp" is same . Also I mentioned that sorting on two fields (actual time
and nominal time) can be done but that is not the right solution as entity
instances can have same actual time and nominal time.
I have suggested just a simple solution to permanently fix it so that
"timestamp" should be unique for each added instance vertex. As currently (and
the example I provided) many instance vertices "timestamp" is not unique.
Moreover, instance actual time and nominal time, can be set as vertex property.
I hope this answers your question.
> 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)
