[
https://issues.apache.org/jira/browse/FALCON-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055707#comment-15055707
]
Peeyush Bishnoi commented on FALCON-1661:
-----------------------------------------
[~ajayyadava] and [~pavan kumar] : As I have mentioned that I need to sort the
Falcon instances on "timestamp" that has been added in GraphDB. Also I
specified that being the Oozie coordinator actual time/created time is getting
used as "timestamp", so same "timestamp" is getting set across many
vertices(example provided above). Due to this sort order of instances is not
coming appropriate.
I could have used nominal time value as well along with "timestamp" (in case,
if two vertices "timestamp" are equal) but it is always good to store the
vertices with unique "timestamp" in GraphDB. Also I have thought to use nominal
time to get unique timestamp, but chances are that nominal time may also be
same across Entity.
> 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)
